feat(docker-build-image): support buildKit configuration #1667
neilime__pull-request-ci.yml
on: pull_request
Matrix: ci / linter / 🛡️ CodeQL Analysis
ci
/
...
/
🧹 Lint Code Base
1m 49s
ci
/
...
/
prepare-actions-linting
8s
ci
/
...
/
Arrange - Prepare variables
5s
ci
/
...
/
prepare-variables
5s
ci
/
...
/
prepare-variables
5s
ci
/
...
/
prepare-variables
4s
ci
/
...
/
Test for "docker/build-image" action
33s
ci
/
...
/
Test for "docker/build-image" action with given tag
36s
ci
/
...
/
Test for "docker/get-image-metadata" action
9s
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
5s
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
5s
Matrix: ci / Test docker build images - Platforms and Signing / act-build-images
ci
/
...
/
prepare-variables
5s
ci
/
...
/
prepare-variables
4s
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
ci
/
...
/
Publish images manifests
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
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
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
0s
ci
/
...
/
cleanup
4s
Annotations
26 errors and 23 warnings
|
ci / Test docker build images - Building / Arrange - Build with args, secrets / Build image test-build-args-secrets for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / test-action-helm-test-chart / build-test-images / Build image application-test for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Multi registry inputs / Act - Build images with structured registry inputs / Build image test-multi-registry-inputs for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-multi-arch-registry for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - signed) / Build image test-pr-648-1667-mono-arch-signed for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / test-action-docker-prune-pull-requests-package-version / Arrange - Build images / Build image test-prune-1667 for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-multi-arch-gha for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-multi-arch-registry for linux/arm64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Caching / Act - Build images - registry cache / Build image test-caching-mono-arch-registry for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-pr-648-1667-multi-arch-unsigned for linux/arm64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / test-action-docker-prune-pull-requests-package-version / Arrange - Build images / Build image test-prune-1667 for linux/arm64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-pr-648-1667-multi-arch-unsigned for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - unsigned) / Build image test-pr-648-1667-mono-arch-unsigned for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-multi-arch-gha for linux/arm64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Caching / Act - Build images - gha cache / Build image test-caching-mono-arch-gha for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-pr-648-1667-multi-arch-signed for linux/arm64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / test-action-helm-release-chart / Test for "helm/release-chart" action with simple chart (umbrella-application, [
{ "file": "char...
Process completed with exit code 1.
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-pr-648-1667-multi-arch-signed for linux/amd64
Failed to get odic token, did you forget the `permissions: { id-token: write }` permission in your caller workflow, alternatively `permissions: write-all` works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
|
|
ci / test-action-helm-release-chart / Test for "helm/release-chart" action with simple chart (application, [
{ "path": ".image.regist...
Process completed with exit code 1.
|
|
ci / test-action-docker-prune-pull-requests-package-version / cleanup
Unhandled error: HttpError: Package not found.
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/hoverkraft-tech/ci-github-container/application-test:pr-648-446d555: denied: installation not allowed to Write organization package
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action with given tag
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/hoverkraft-tech/ci-github-container/application-test:0.1.0: denied: installation not allowed to Write organization package
|
|
ci / Test docker build images - Platforms and Signing / Cleanup ephemeral test packages (multi-arch - signed, test-pr-648-1667-multi-arch-signed, ["linux...
Unhandled error: HttpError: Package not found.
|
|
ci / Test docker build images - Platforms and Signing / Cleanup ephemeral test packages (multi-arch - unsigned, test-pr-648-1667-multi-arch-unsigned, ["l...
Unhandled error: HttpError: Package not found.
|
|
ci / Test docker build images - Platforms and Signing / Cleanup ephemeral test packages (mono-arch - unsigned, test-pr-648-1667-mono-arch-unsigned, ["lin...
Unhandled error: HttpError: Package not found.
|
|
ci / Test docker build images - Platforms and Signing / Cleanup ephemeral test packages (mono-arch - signed, test-pr-648-1667-mono-arch-signed, ["linux/a...
Unhandled error: HttpError: Package not found.
|
|
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 - 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. 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. 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 - 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. 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. 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-648-1667-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. 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-1667 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. 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. 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. 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. 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-1667 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. 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-648-1667-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. 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-648-1667-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. 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. 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. 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-648-1667-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. 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-release-chart / Test for "helm/release-chart" action with simple chart (umbrella-application, [
{ "file": "char...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@1a275c3b69536ee54be43f2070a358922e12c8d4. 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/
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-pr-648-1667-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. 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-release-chart / Test for "helm/release-chart" action with simple chart (application, [
{ "path": ".image.regist...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@1a275c3b69536ee54be43f2070a358922e12c8d4. 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/
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: int128/docker-build-cache-config-action@3a4a4fababc091be29633e5a2b3bbf523996802a, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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/
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action
ERROR: no builder "builder-710b7a41-3233-4b7d-8838-3634dbe459ce" found
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action with given tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: int128/docker-build-cache-config-action@3a4a4fababc091be29633e5a2b3bbf523996802a, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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/
|
|
ci / test-action-docker-build-image / Test for "docker/build-image" action with given tag
ERROR: no builder "builder-0054246b-2047-4a85-8896-14579add2224" found
|