chore(deps): bump yaml in /actions/helm/release-chart #646
neilime__main-ci.yml
on: push
Matrix: ci / linter / 🛡️ CodeQL Analysis
ci
/
...
/
🧹 Lint Code Base
2m 0s
ci
/
...
/
prepare-actions-linting
5s
ci
/
...
/
Arrange - Prepare variables
5s
Matrix: ci / test-action-helm-release-chart / Test for "helm/release-chart" action with simple chart
ci
/
...
/
Test for "docker/build-image" action
47s
ci
/
...
/
Test for "docker/build-image" action with given tag
46s
ci
/
...
/
Test for "docker/build-image" action with BuildKit daemon config
29s
ci
/
...
/
Test for "docker/get-image-metadata" action
7s
ci
/
...
/
Test for "docker/get-image-metadata" action with given tag
7s
ci
/
...
/
Test for "docker/get-image-name" action
7s
ci
/
...
/
Test for "docker/get-image-name" action with given repository
5s
ci
/
...
/
Test for "helm/parse-chart-uri" action
7s
ci
/
...
/
prepare-variables
4s
ci
/
...
/
prepare-variables
5s
ci
/
...
/
prepare-variables
6s
ci
/
...
/
prepare-variables
4s
Matrix: ci / Test docker build images - Platforms and Signing / act-build-images
ci
/
...
/
prepare-variables
3s
ci
/
...
/
prepare-variables
3s
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
41s
ci
/
...
/
Publish images manifests
48s
ci
/
...
/
Publish images manifests
30s
ci
/
...
/
Publish images manifests
52s
Matrix: ci / Test docker build images - Platforms and Signing / Cleanup ephemeral test packages
ci
/
...
/
Publish images manifests
30s
ci
/
...
/
Publish images manifests
36s
ci
/
...
/
Test for "helm/test-chart" action
1m 50s
ci
/
...
/
Assert - Build with args, secrets
7s
ci
/
...
/
Assert - Build images with structured registry inputs
15s
ci
/
...
/
Arrange - Verify built images
11s
Matrix: ci / Test docker build images - Caching / assert-images-cache
ci
/
...
/
Act - Prune pull requests image tags
24s
ci
/
...
/
Assert - Verify deleted image tags
6s
helm-docs
31s
sync-docs
/
prepare-and-dispatch
Annotations
64 warnings
|
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. 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-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 with BuildKit daemon config
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@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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-build-image / Test for "docker/build-image" action with BuildKit daemon config
ERROR: no builder "builder-6c12ce70-1ff9-4483-a011-9cb2ef1192ec" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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 - Multi registry inputs / Act - Build images with structured registry inputs / Build image test-multi-registry-inputs for linux/amd64
ERROR: no builder "builder-abf84959-b322-4b8e-a024-d94b65499b13" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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
ERROR: no builder "builder-869f487e-da15-4564-8133-e75694d6b59a" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-main-646-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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, 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 docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-main-646-multi-arch-unsigned for linux/amd64
ERROR: no builder "builder-de4d1922-7db2-493c-8b32-192048e155a9" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, 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 docker build images - Caching / Act - Build images - registry cache / Build image test-caching-mono-arch-registry for linux/amd64
ERROR: no builder "builder-38bd0190-8a2c-4c39-85c6-e0e42c15a519" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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
ERROR: no builder "builder-9d7beffe-59b6-4af8-b188-a2a49fea11a2" 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@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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-build-image / Test for "docker/build-image" action with given tag
ERROR: no builder "builder-cadc705b-2308-418b-b201-adce6a17dc81" found
|
|
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@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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-build-image / Test for "docker/build-image" action
ERROR: no builder "builder-e6b19385-18a4-424d-aa3c-e90c69895b66" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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
ERROR: no builder "builder-04ec2946-b4a1-411e-9c7a-81532a3f3c05" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, 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-helm-test-chart / build-test-images / Build image application-test for linux/amd64
ERROR: no builder "builder-ebbd0a58-fa15-4e35-b9a9-d2f7cd4f4965" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - unsigned) / Build image test-main-646-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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, 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 docker build images - Platforms and Signing / Act - Build images (mono-arch - unsigned) / Build image test-main-646-mono-arch-unsigned for linux/amd64
ERROR: no builder "builder-5091a7bf-51a2-435d-b84b-7fc0ceb7d127" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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
ERROR: no builder "builder-b0311df6-b514-44eb-ba45-7c113da7bc06" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-main-646-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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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-main-646-multi-arch-signed for linux/arm64
ERROR: no builder "builder-dbac6ced-aecf-47ff-8969-1e96604e89f5" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - signed) / Build image test-main-646-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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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-main-646-multi-arch-signed for linux/amd64
ERROR: no builder "builder-34efe42f-b36b-414a-b05e-97fdb29647c7" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - signed) / Build image test-main-646-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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, 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 docker build images - Platforms and Signing / Act - Build images (mono-arch - signed) / Build image test-main-646-mono-arch-signed for linux/amd64
ERROR: no builder "builder-a7c61ac1-8211-48eb-88f6-828982b78bd6" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Build image test-main-646-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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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-main-646-multi-arch-unsigned for linux/arm64
ERROR: no builder "builder-f067eec2-2078-49eb-a43c-e75f05c3d5ff" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, 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 docker build images - Caching / Act - Build images - gha cache / Build image test-caching-mono-arch-gha for linux/amd64
ERROR: no builder "builder-f4cd4982-d5d6-4852-84c6-25afb0319dce" found
|
|
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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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
ERROR: no builder "builder-38147534-91fa-4fb4-9d31-fe5be448da7f" found
|
|
ci / Test docker build images - Multi registry inputs / Act - Build images with structured registry inputs / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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-646 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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, 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-prune-pull-requests-package-version / Arrange - Build images / Build image test-prune-646 for linux/amd64
ERROR: no builder "builder-2f248ea3-7759-4276-893e-1aefcff33a8d" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (mono-arch - unsigned) / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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-646 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, int128/docker-build-cache-config-action@e9137bc69df98d2aeb47c8cb6e78e8ab2f13abb7, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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-646 for linux/arm64
ERROR: no builder "builder-72a51b2c-2304-42ff-9cd0-fde9cd62fced" found
|
|
ci / Test docker build images - Platforms and Signing / Act - Build images (multi-arch - unsigned) / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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 - Building / Arrange - Build with args, secrets / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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 / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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 / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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 / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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) / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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) / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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 / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, geekyeggo/delete-artifact@f275313e70c08f6120db482d7a6b98377786765b. 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 / Act - Prune pull requests image tags
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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 / Test for "helm/test-chart" action
No file matched to [/home/runner/work/ci-github-container/ci-github-container/**/*requirements*.txt,/home/runner/work/ci-github-container/ci-github-container/**/*requirements*.in,/home/runner/work/ci-github-container/ci-github-container/**/*constraints*.txt,/home/runner/work/ci-github-container/ci-github-container/**/*constraints*.in,/home/runner/work/ci-github-container/ci-github-container/**/pyproject.toml,/home/runner/work/ci-github-container/ci-github-container/**/uv.lock,/home/runner/work/ci-github-container/ci-github-container/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
ci / test-action-helm-test-chart / Test for "helm/test-chart" action
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
clean-with-cache / Prune pull requests image tags for test-caching-mono-arch-registry/cache
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|
|
helm-docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: losisin/helm-docs-github-action@6f957579ac122ecc167bf515fe84e828686c9a15. 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/
|
|
clean-with-cache / Prune pull requests image tags for test-caching-multi-arch-registry/cache
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|
|
clean-with-cache / Prune pull requests image tags for test-caching-mono-arch-registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|
|
clean / Prune pull requests image tags for test-caching-mono-arch-gha
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|
|
clean-with-cache / Prune pull requests image tags for test-caching-multi-arch-registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|
|
clean / Prune pull requests image tags for test-caching-multi-arch-gha
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|
|
clean / Prune pull requests image tags for test-build-args-secrets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|
|
clean / Prune pull requests image tags for application-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, dataaxiom/ghcr-cleanup-action@cd0cdb900b5dbf3a6f2cc869f0dbb0b8211f50c4. 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/
|