Skip to content

✨ Add daemon package version mismatch warning #7318 #2018

✨ Add daemon package version mismatch warning #7318

✨ Add daemon package version mismatch warning #7318 #2018

Triggered via push April 29, 2026 20:12
Status Success
Total duration 30m 12s
Artifacts 2

docker.yml

on: push
build-amd64  /  linux/amd64
2m 45s
build-amd64 / linux/amd64
Matrix: test-amd64
build  /  linux/amd64,linux/arm64
11m 21s
build / linux/amd64,linux/arm64
Matrix: publish-ghcr / release
Matrix: publish-dockerhub / release
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build-amd64 / linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/bake-action@v6.10.0, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 / 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/bake-action@v6.10.0, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
publish-ghcr / release (aiida-core-with-services)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: akhilerm/tag-push-action@v2.2.0, docker/metadata-action@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
publish-ghcr / release (aiida-core-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: akhilerm/tag-push-action@v2.2.0, docker/metadata-action@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
publish-ghcr / release (aiida-core-base)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: akhilerm/tag-push-action@v2.2.0, docker/metadata-action@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
publish-dockerhub / release (aiida-core-with-services)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: akhilerm/tag-push-action@v2.2.0, docker/metadata-action@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
publish-dockerhub / release (aiida-core-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: akhilerm/tag-push-action@v2.2.0, docker/metadata-action@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
publish-dockerhub / release (aiida-core-base)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: akhilerm/tag-push-action@v2.2.0, docker/metadata-action@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
aiidateam~aiida-core~IONKGC+2.dockerbuild
906 KB
sha256:ccc98320efdfb72b521bd26e9412e81fe8ce3e69579a772c9364c063d7de1cc6
aiidateam~aiida-core~QA8JEE+2.dockerbuild
530 KB
sha256:81f40b32f068acae569d95b40b5ccdf6edd00a5da6cb321a3ef685c82ed64770