build(deps): bump fast-xml-parser from 5.4.2 to 5.5.7 #2845
dependabot[bot]ci.yml
on: pull_request
multi
13s
error
24s
debug
18s
docker-driver
5s
endpoint
47s
buildkitd-config
12s
buildkitd-config-inline
15s
standalone-cmd
15s
standalone-action
13s
append
17s
platforms
16s
docker-context
5s
windows-error
29s
keep-state
15s
keep-state-error
5s
Matrix: build-ref
Matrix: cache-binary
Matrix: cleanup
Matrix: driver
Matrix: k3s
Matrix: main
Matrix: use
Matrix: with-qemu
Annotations
9 errors and 21 warnings
|
keep-state-error
Cannot use keep-state with docker driver
|
|
error
ERROR: failed to initialize builder builder-e9f9c960-25bd-46b8-bd26-dc3cf5f4a468 (builder-e9f9c960-25bd-46b8-bd26-dc3cf5f4a4680): 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 (refs/pull/731/head)
Canceling since a higher priority waiting request for ci-refs/pull/496/merge exists
|
|
build-ref (refs/tags/v0.5.1)
Canceling since a higher priority waiting request for ci-refs/pull/496/merge exists
|
|
build-ref (master)
Canceling since a higher priority waiting request for ci-refs/pull/496/merge exists
|
|
build-ref (master)
The operation was canceled.
|
|
build-ref (cb185f095fd3d9444e0aa605d3789e9e05f2a1e7)
Canceling since a higher priority waiting request for ci-refs/pull/496/merge exists
|
|
ci
Canceling since a higher priority waiting request for ci-refs/pull/496/merge exists
|
|
cache-binary (true)
Failed to restore:
|
|
main (v0.4.1)
Failed to restore:
|
|
with-qemu (all)
Failed to restore:
|
|
with-qemu (v0.9.1, all)
Failed to restore:
|
|
with-qemu (v0.9.1, all)
Failed to restore:
|
|
platforms
Failed to restore:
|
|
with-qemu (v0.9.1, arm64,riscv64,arm)
Failed to restore:
|
|
with-qemu (v0.9.1, arm64,riscv64,arm)
Failed to restore:
|
|
debug
Failed to restore:
|
|
with-qemu (arm64,riscv64,arm)
Failed to restore:
|
|
main (cloud:v0.11.2-desktop.2)
Failed to restore:
|
|
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/
|
|
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/
|
|
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.11.0)
Failed to restore:
|
|
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 (v0.10.5)
Failed to restore:
|
|
build-ref (refs/pull/731/head)
Failed to restore:
|
|
build-ref (refs/tags/v0.5.1)
Attestations are only supported by buildx >= 0.10.0; the inputs 'attests', 'provenance' and 'sbom' are ignored.
|
|
build-ref (refs/tags/v0.5.1)
Failed to restore:
|
|
build-ref (cb185f095fd3d9444e0aa605d3789e9e05f2a1e7)
Failed to restore:
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
docker~setup-buildx-action~FA7GN9.dockerbuild
|
14.3 KB |
sha256:79bce63045a785be955cd0344f8b011912ab983992975041490280a261deb2c4
|
|
|
docker~setup-buildx-action~GZQEC9.dockerbuild
|
18.2 KB |
sha256:cf4b4fdd48db1886d09ad01934d5bf8c7e17d5d3ce5d2bdd192c9f82eadaf615
|
|
|
docker~setup-buildx-action~HIU6AR.dockerbuild
|
16.3 KB |
sha256:c1dcca391ec8519615bb80776a11ac0e6b33f0b58e08aed48005bbbfed1b7405
|
|
|
docker~setup-buildx-action~P9UWOZ.dockerbuild
|
42.4 KB |
sha256:dd17975c68bfcccae7d60a40421a1fbf2422e93cfe3ee6a1c8d9e175d425ce59
|
|
|
docker~setup-buildx-action~Y56FWM.dockerbuild
|
16.1 KB |
sha256:62bf9b3fc5aecd12817616d142d36bff0353fb0d6d721a5a428b0846389ee150
|
|