Skip to content
Docker Image Build

chore(deps): bump the minor-security group across 2 directories with … #450

Sign in to view logs

chore(deps): bump the minor-security group across 2 directories with …

chore(deps): bump the minor-security group across 2 directories with … #450

Triggered via push June 16, 2026 18:59
@emilyjablonskiemilyjablonski
pushed 1e941d5
main
Status Success
Total duration 5m 14s
Artifacts 8

docker_image_build.yml

on: push
Matrix: build-image
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build-image (dbinit, {{defaultContext}}:api/dbinit, Dockerfile, linux/amd64)
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
build-image (infra-dev, {{defaultContext}}:infra, Dockerfile.dev, linux/amd64,linux/arm64)
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
build-image (infra, {{defaultContext}}:infra, Dockerfile, linux/amd64,linux/arm64)
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
build-image (aws-otel-collector, {{defaultContext}}:infra/aws-otel-collector, Dockerfile, linux/a...
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
build-image (dbseed, {{defaultContext}}:api, Dockerfile.dbseed, linux/amd64)
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
build-image (api, {{defaultContext}}:api, Dockerfile, linux/amd64)
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
build-image (public, {{defaultContext}}, Dockerfile.sites.public, linux/amd64)
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
build-image (partners, {{defaultContext}}, Dockerfile.sites.partners, linux/amd64)
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.18.0, docker/login-action@v3.6.0, docker/setup-buildx-action@v3.11.1, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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
bloom-housing~bloom~56X2E6.dockerbuild
71.1 KB
sha256:8d554a85c89e7c8abba65a1ef1cb24b6a176600436ed8768a5492915be6de53d
bloom-housing~bloom~8JENSD.dockerbuild
89.3 KB
sha256:d09ad6402698fa9719145e541bc15cb0549b75ee1fa825ba77c869e34e95ac1a
bloom-housing~bloom~A3104N.dockerbuild
83.7 KB
sha256:e83b1580b1a959d6be14d594d7be534035e4ff912ecfedc9614a50612f3b2dd4
bloom-housing~bloom~DCOG5B.dockerbuild
104 KB
sha256:380e3059e0b3df2a9e396182525a4d2e48bef20ac549fc8b77a5f447cc00ff9c
bloom-housing~bloom~JONBCX.dockerbuild
93 KB
sha256:1fe84a073d32f67aaa6d0e63433640519c66339556ebb89701d5cc468589f451
bloom-housing~bloom~TXR5U9.dockerbuild
91.9 KB
sha256:782e57f5cef89a1678df880e6c29075db9691e1405042997149673aada5e429d
bloom-housing~bloom~UV1HYY.dockerbuild
63.6 KB
sha256:372d413c827f090fe2a27879eab4c72f09864fc89111d818d679c73155adddfd
bloom-housing~bloom~W61BMX.dockerbuild
110 KB
sha256:1fdae27b93894848c7fc8fcb06c0836bbba0780e95b4e8582b3316715c799e88