Skip to content

fix: full routing patch, SSL disable, seed with correct fields, user … #8

fix: full routing patch, SSL disable, seed with correct fields, user …

fix: full routing patch, SSL disable, seed with correct fields, user … #8

Triggered via push March 17, 2026 15:33
Status Success
Total duration 2m 20s
Artifacts 2
Check for Docker changes
Check for Docker changes
Build BOPS Back-Office
2m 14s
Build BOPS Back-Office
Build BOPS Applicants Portal
26s
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~43GVD5.dockerbuild
71.4 KB
sha256:01f39db09b76cd61880b2ed71eebfc73700c16834a5d283bb9bae2b7b36e89ad
co-cddo~ndx_try_aws_scenarios~QKA6I6.dockerbuild
64.4 KB
sha256:553dc74866d97784a76050171478f232a2c05e1d063e7a0d3503de8c8897a505