Skip to content

Bump docker/login-action from 3 to 4 #24

Bump docker/login-action from 3 to 4

Bump docker/login-action from 3 to 4 #24

Triggered via pull request March 19, 2026 17:44
Status Success
Total duration 3m 7s
Artifacts 6

build.yml

on: pull_request
Matrix: Build Images
Matrix: Test Images
Matrix: Promote to Production
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Build Images (3.9, bullseye)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5. 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/
Build Images (3.11, bookworm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5. 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/
Build Images (3.10, bullseye)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5. 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/
Build Images (3.12, bookworm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5. 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/
Build Images (3.13, bookworm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5. 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/
Build Images (3.14, bookworm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5. 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
jski~python-container-builder~G230R7.dockerbuild
123 KB
sha256:62face27b5b0ef2e12005684cb7af7b2c5954d9d3b58fcb7e3884bd4727f47ee
jski~python-container-builder~M8UYVD.dockerbuild
120 KB
sha256:634322ad41a7c9c7b4ab734bb84fac64df937f4075acf67232e4bbc7af134d1d
jski~python-container-builder~P6TJRC.dockerbuild
119 KB
sha256:16c957ab8dcd710d615c2c4ca5c95dc335cad4b4c7613417ec7d8f36b7494fc8
jski~python-container-builder~PRCZ6R.dockerbuild
120 KB
sha256:8ff9ecf321d24244bba798f0d170c26d38372d9a3e9a7231a6f988c326590523
jski~python-container-builder~S8Y4J3.dockerbuild
122 KB
sha256:4f720f30986d8caf749eeee33152f458a0fdd9d03f69ae09db333c64af403f79
jski~python-container-builder~YWIAT8.dockerbuild
122 KB
sha256:5b89b2858b54d09d6fcd0aed826710241723811ab856185b0b94d5399fb292dd