Skip to content

chore(deps): update containerbase/internal-tools action to v4.5.27 #3375

chore(deps): update containerbase/internal-tools action to v4.5.27

chore(deps): update containerbase/internal-tools action to v4.5.27 #3375

Triggered via push April 20, 2026 03:23
Status Failure
Total duration 2m 9s
Artifacts

build.yml

on: push
Matrix: test
release
0s
release
success
2s
success
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 3 warnings
test (macos-latest, node-20)
Process completed with exit code 1.
test (macos-latest)
The strategy configuration was canceled because "test.macos-latest_20" failed
test (ubuntu-latest)
The strategy configuration was canceled because "test.macos-latest_20" failed
test (ubuntu-latest)
The operation was canceled.
test (ubuntu-latest, node-20)
The strategy configuration was canceled because "test.macos-latest_20" failed
test (ubuntu-latest, node-20)
The operation was canceled.
test (macos-latest, node-24)
The strategy configuration was canceled because "test.macos-latest_20" failed
test (macos-latest, node-24)
The operation was canceled.
test (windows-latest, node-24)
The strategy configuration was canceled because "test.macos-latest_20" failed
test (windows-latest, node-24)
Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
test (windows-latest, node-24)
The operation was canceled.
test (windows-latest)
The strategy configuration was canceled because "test.macos-latest_20" failed
test (windows-latest)
Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
test (windows-latest)
The operation was canceled.
test (windows-latest, node-20)
The strategy configuration was canceled because "test.macos-latest_20" failed
test (windows-latest, node-20)
Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
test (windows-latest, node-20)
The operation was canceled.
success
Process completed with exit code 1.
test (ubuntu-latest, node-24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test (macos-latest, node-20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test (ubuntu-latest, node-20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/