Skip to content

build(deps): bump the npm_and_yarn group across 1 directory with 3 updates #2840

build(deps): bump the npm_and_yarn group across 1 directory with 3 updates

build(deps): bump the npm_and_yarn group across 1 directory with 3 updates #2840

Triggered via pull request March 18, 2026 01:57
Status Cancelled
Total duration 1m 6s
Artifacts 5

ci.yml

on: pull_request
multi
14s
multi
error
21s
error
debug
23s
debug
docker-driver
8s
docker-driver
endpoint
51s
endpoint
buildkitd-config
19s
buildkitd-config
buildkitd-config-inline
14s
buildkitd-config-inline
standalone-cmd
12s
standalone-cmd
standalone-action
12s
standalone-action
append
10s
append
platforms
18s
platforms
docker-context
9s
docker-context
windows-error
47s
windows-error
keep-state
11s
keep-state
keep-state-error
4s
keep-state-error
Matrix: build-ref
Matrix: cache-binary
Matrix: cleanup
Matrix: driver
Matrix: k3s
Matrix: main
Matrix: use
Matrix: with-qemu
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 5 warnings
keep-state-error
Cannot use keep-state with docker driver
error
ERROR: failed to initialize builder builder-222c0913-e82b-4cd1-815d-494f4eb2537f (builder-222c0913-e82b-4cd1-815d-494f4eb2537f0): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
windows-error
ERROR: no matching manifest for windows(10.0.26100)/amd64 in the manifest list entries
build-ref (master)
Canceling since a higher priority waiting request for ci-refs/pull/494/merge exists
build-ref (master)
The operation was canceled.
ci
Canceling since a higher priority waiting request for ci-refs/pull/494/merge exists
error
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
build-ref (refs/tags/v0.5.1)
Attestations are only supported by buildx >= 0.10.0; the inputs 'attests', 'provenance' and 'sbom' are ignored.
k3s (v0.11.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
k3s (v0.10.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
k3s (latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/

Artifacts

Produced during runtime
Name Size Digest
docker~setup-buildx-action~8SDE9V.dockerbuild
53.2 KB
sha256:ead2597ec99623eec5de80ebf3969bbbdc4ad1f97c05038e344df043e30eecb2
docker~setup-buildx-action~OABKRF.dockerbuild
13.2 KB
sha256:af17525b0f02c3c838eb760163336e23b51527d9ef357df4f1d1d71abf551561
docker~setup-buildx-action~QBHXBK.dockerbuild
20.1 KB
sha256:ef9d198e6ef838a7fbf517291a79e3210d9a7c5709b72c7685bc35663f0170f3
docker~setup-buildx-action~QND1OB.dockerbuild
21.9 KB
sha256:58d9566a0cfcce2f1b965bdfa3af0acff63e0b8ff82204d1ac8579ce4d0ba05d
docker~setup-buildx-action~Y8CEYY.dockerbuild
20.3 KB
sha256:870e182e31d6f210fa2715cead31e0ccbcfdb05c2f239b972f1c25ecbf06c624