Skip to content

🧪 Add workflow_dispatch trigger to test-install (#7330) #2013

🧪 Add workflow_dispatch trigger to test-install (#7330)

🧪 Add workflow_dispatch trigger to test-install (#7330) #2013

Triggered via push April 22, 2026 08:09
Status Success
Total duration 20m 25s
Artifacts 2

docker.yml

on: push
build-amd64  /  linux/amd64
1m 57s
build-amd64 / linux/amd64
Matrix: test-amd64
build  /  linux/amd64,linux/arm64
12m 17s
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-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-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-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-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/

Artifacts

Produced during runtime
Name Size Digest
aiidateam~aiida-core~OFPTFG+2.dockerbuild
417 KB
sha256:6fdbb7f5ca812858e805f348337eb999d2c9e36c161e5e0c62c93360d26ac002
aiidateam~aiida-core~Q6D3D0+2.dockerbuild
896 KB
sha256:460172aefd5a5e9fe8581178affdc9fe69b3f055997f29a1caf6bc779fdc0fe0