Skip to content

Fix image-upload leakage across shared records + finish pala→primo re… #190

Fix image-upload leakage across shared records + finish pala→primo re…

Fix image-upload leakage across shared records + finish pala→primo re… #190

Triggered via push June 25, 2026 19:02
Status Failure
Total duration 5m 8s
Artifacts 1

main.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
deploy-testing
Process completed with exit code 1.
build-image
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L40
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "PRIMO_USER_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L38
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "PRIMO_SUPERUSER_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
deploy-testing
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
primocms~primo~9USRQ8.dockerbuild
104 KB
sha256:5211ab27d610913603f233d55c8690a04d2e24823bb328f81440bc18e2491e80