Skip to content

fix: move ApiUser creation outside 'unless assessor' guard so it runs… #15

fix: move ApiUser creation outside 'unless assessor' guard so it runs…

fix: move ApiUser creation outside 'unless assessor' guard so it runs… #15

Triggered via push March 18, 2026 10:12
Status Success
Total duration 2m 39s
Artifacts 2
Check for Docker changes
0s
Check for Docker changes
Build BOPS Back-Office
2m 36s
Build BOPS Back-Office
Build BOPS Applicants Portal
29s
Build BOPS Applicants Portal
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Build BOPS Applicants Portal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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: bops-applicants-src/Dockerfile.production#L127
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SECRET_KEY_BASE") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Build BOPS Back-Office
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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
co-cddo~ndx_try_aws_scenarios~JG1E9N.dockerbuild
72.7 KB
sha256:8a45732fe2fd88e570395081d80c91e5c97a809952c5ec5b8614deea706a72c4
co-cddo~ndx_try_aws_scenarios~PYAAP9.dockerbuild
63.2 KB
sha256:0bd29b3b3622e0d3ed1407d1b6253c4d3a9f04ca68f1432b5ec9e064c9d40544