Skip to content

fix: guard nil subdomain in middleware, use TCP check for applicants … #5

fix: guard nil subdomain in middleware, use TCP check for applicants …

fix: guard nil subdomain in middleware, use TCP check for applicants … #5

Triggered via push March 17, 2026 10:50
Status Success
Total duration 3m 10s
Artifacts 2
Check for Docker changes
Check for Docker changes
Build BOPS Back-Office
3m 6s
Build BOPS Back-Office
Build BOPS Applicants Portal
1m 41s
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~71QUG0.dockerbuild
72.1 KB
sha256:db7425871375fbbbc0f376cc7ed617631e8b0ef5eee328181d9d5c49c65a1f46
co-cddo~ndx_try_aws_scenarios~M8TR0Q.dockerbuild
62.8 KB
sha256:62cfe6dfa0c94d1098859a17bac8ee058dcc9f32f791db43181c14be8d9665af