Skip to content

Fix: Remove glob character escaping for SCP RCP protocol (#7335) #2030

Fix: Remove glob character escaping for SCP RCP protocol (#7335)

Fix: Remove glob character escaping for SCP RCP protocol (#7335) #2030

Triggered via push May 13, 2026 08:29
Status Success
Total duration 34m 16s
Artifacts 2

docker.yml

on: push
build-amd64  /  linux/amd64
2m 39s
build-amd64 / linux/amd64
Matrix: test-amd64
build  /  linux/amd64,linux/arm64
24m 49s
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-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-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-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-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-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/

Artifacts

Produced during runtime
Name Size Digest
aiidateam~aiida-core~1GKSJ6+2.dockerbuild
918 KB
sha256:5f4bcce1580dc9354a763385f71c971425e81f382d08f553109d847743ac2eed
aiidateam~aiida-core~WDV82I+2.dockerbuild
430 KB
sha256:e69eaffc0972fa3894b83dd2424ffd248113e32be0a1f2981d70cb6fb5450b79