fix(docker/build-image): prevent random failure on post action because of buildx and cache #1712
neilime__pull-request-ci.yml
on: pull_request
Matrix: ci / linter / 🛡️ CodeQL Analysis
ci
/
...
/
🧹 Lint Code Base
1m 46s
ci
/
...
/
prepare-actions-linting
8s
ci
/
...
/
Arrange - Prepare variables
4s
ci
/
...
/
prepare-variables
4s
ci
/
...
/
prepare-variables
6s
ci
/
...
/
prepare-variables
3s
ci
/
...
/
Test for "docker/build-image" action
11s
ci
/
...
/
Test for "docker/build-image" action with given tag
14s
ci
/
...
/
Test for "docker/build-image" action with BuildKit daemon config
7s
ci
/
...
/
Test for "docker/get-image-metadata" action
10s
ci
/
...
/
Test for "docker/get-image-metadata" action with given tag
11s
ci
/
...
/
Test for "docker/get-image-name" action
5s
ci
/
...
/
Test for "docker/get-image-name" action with given repository
3s
ci
/
...
/
Test for "helm/parse-chart-uri" action
7s
Matrix: ci / test-action-helm-release-chart / Test for "helm/release-chart" action with simple chart
ci
/
...
/
prepare-variables
6s
Matrix: ci / Test docker build images - Platforms and Signing / act-build-images
ci
/
...
/
prepare-variables
6s
ci
/
...
/
prepare-variables
6s
Matrix: ci / test-action-helm-test-chart / build-test-images / build-images
Matrix: ci / Test docker build images - Building / Arrange - Build with args, secrets / build-images
Matrix: ci / Test docker build images - Multi registry inputs / Act - Build images with structured registry inputs / build-images
Matrix: ci / test-action-docker-prune-pull-requests-package-version / Arrange - Build images / build-images
Matrix: ci / Test docker build images - Platforms and Signing / assert-images-signature
Matrix: ci / Test docker build images - Platforms and Signing / assert-images-versions
Matrix: ci / Test docker build images - Caching / Act - Build images - gha cache / build-images
Matrix: ci / Test docker build images - Caching / Act - Build images - registry cache / build-images
ci
/
...
/
Publish images manifests
0s
ci
/
...
/
Publish images manifests
0s
ci
/
...
/
Publish images manifests
0s
ci
/
...
/
Publish images manifests
0s
Matrix: ci / Test docker build images - Platforms and Signing / Cleanup ephemeral test packages
ci
/
...
/
Publish images manifests
0s
ci
/
...
/
Publish images manifests
0s
ci
/
...
/
Test for "helm/test-chart" action
0s
ci
/
...
/
Assert - Build with args, secrets
0s
ci
/
...
/
Assert - Build images with structured registry inputs
0s
ci
/
...
/
Arrange - Verify built images
0s
Matrix: ci / Test docker build images - Caching / assert-images-cache
ci
/
...
/
Act - Prune pull requests image tags
0s
ci
/
...
/
Assert - Verify deleted image tags
ci
/
...
/
cleanup
4s
Annotations
27 errors and 19 warnings
|
ci / test-action-docker-build-image / Test for "docker/build-image" action with BuildKit daemon config
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-get-image-metadata / Test for "docker/get-image-metadata" action
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/get-image-name'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-get-image-metadata / Test for "docker/get-image-metadata" action with given tag
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/get-image-name'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action with given tag
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Multi registry inputs / Act - Build images with structured registry inputs / Build image test-multi-registry-inputs for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-helm-test-chart / build-test-images / Build image application-test for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Building / Arrange - Build with args, secrets / Build image test-build-args-secrets for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-docker-prune-pull-requests-package-version / Arrange - Build images / Build image test-prune-1712 for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-pr-721-1712-multi-arch-signed for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - signed) / Build image test-pr-721-1712-mono-arch-signed for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-pr-721-1712-multi-arch-signed for linux/arm64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-pr-721-1712-multi-arch-unsigned for linux/arm64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-docker-prune-pull-requests-package-version / Arrange - Build images / Build image test-prune-1712 for linux/arm64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-pr-721-1712-multi-arch-unsigned for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-multi-arch-gha for linux/arm64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-multi-arch-gha for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - unsigned) / Build image test-pr-721-1712-mono-arch-unsigned for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-mono-arch-gha for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-multi-arch-registry for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-mono-arch-registry for linux/amd64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
ci / test-action-docker-prune-pull-requests-package-version / cleanup
Unhandled error: HttpError: Package not found. - https://docs.github.com/rest/packages/packages#delete-a-package-for-an-organization
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-multi-arch-registry for linux/arm64
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/ci-github-container/self-actions/docker/setup'. Did you forget to run actions/checkout before running your local action?
|
|
|
|
|
|
|
|
|
|
ci / linter / 🛡️ CodeQL Analysis (actions)
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses.
To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.
|
|
ci / linter / 🛡️ CodeQL Analysis (actions)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
ci / Test docker build images - Multi registry inputs / Act - Build images with structured registry inputs / Build image test-multi-registry-inputs for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / test-action-helm-test-chart / build-test-images / Build image application-test for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Building / Arrange - Build with args, secrets / Build image test-build-args-secrets for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / test-action-docker-prune-pull-requests-package-version / Arrange - Build images / Build image test-prune-1712 for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-pr-721-1712-multi-arch-signed for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - signed) / Build image test-pr-721-1712-mono-arch-signed for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-pr-721-1712-multi-arch-signed for linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-pr-721-1712-multi-arch-unsigned for linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / test-action-docker-prune-pull-requests-package-version / Arrange - Build images / Build image test-prune-1712 for linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-pr-721-1712-multi-arch-unsigned for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-multi-arch-gha for linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-multi-arch-gha for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - unsigned) / Build image test-pr-721-1712-mono-arch-unsigned for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-mono-arch-gha for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-multi-arch-registry for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-mono-arch-registry for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-multi-arch-registry for linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|