Skip to content

ci: bump crazy-max/.github to 1.1.0 #2858

ci: bump crazy-max/.github to 1.1.0

ci: bump crazy-max/.github to 1.1.0 #2858

Triggered via pull request March 25, 2026 11:40
Status Success
Total duration 1m 7s
Artifacts 6

ci.yml

on: pull_request
multi
15s
multi
error
20s
error
debug
27s
debug
docker-driver
7s
docker-driver
endpoint
47s
endpoint
buildkitd-config
12s
buildkitd-config
buildkitd-config-inline
11s
buildkitd-config-inline
standalone-cmd
14s
standalone-cmd
standalone-action
16s
standalone-action
append
16s
append
platforms
15s
platforms
docker-context
6s
docker-context
windows-error
25s
windows-error
keep-state
9s
keep-state
keep-state-error
5s
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

3 errors and 18 warnings
keep-state-error
Cannot use keep-state with docker driver
error
ERROR: failed to initialize builder builder-b2cae08d-b1d9-4cf9-9fdd-ec9cd03639cd (builder-b2cae08d-b1d9-4cf9-9fdd-ec9cd03639cd0): 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
main (cloud:v0.11.2-desktop.2)
Failed to restore:
with-qemu (v0.9.1, all)
Failed to restore:
with-qemu (v0.9.1, all)
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:
cache-binary (true)
Failed to restore:
platforms
Failed to restore:
with-qemu (all)
Failed to restore:
main (v0.4.1)
Failed to restore:
with-qemu (arm64,riscv64,arm)
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/
debug
Failed to restore:
k3s (v0.10.5)
Failed to restore:
k3s (v0.11.0)
Failed to restore:
build-ref (refs/pull/731/head)
Failed to restore:
build-ref (cb185f095fd3d9444e0aa605d3789e9e05f2a1e7)
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:

Artifacts

Produced during runtime
Name Size Digest
docker~setup-buildx-action~P4MLH9.dockerbuild
16.4 KB
sha256:66bc2944a7940d904f86167064260c0253e2604c2241a67de784d1979d7a314f
docker~setup-buildx-action~PGLFSD.dockerbuild
16.3 KB
sha256:35872c71e499d81e2002ab55c29aceff0c2b37f624577a229c1d21eccdd4d912
docker~setup-buildx-action~T1W006.dockerbuild
37 KB
sha256:d6e6f0bc7fb43c545b333daba2005e12316cc5b6579e0f9993c84c08c63e1bda
docker~setup-buildx-action~YU31TL.dockerbuild
14.4 KB
sha256:00b21116070531da83790d6062704b477d851445270fc5f293823a6204ca5f23
docker~setup-buildx-action~YY9MRI.dockerbuild
13.2 KB
sha256:7c20368c86e2d12a7ddb713e0dd9bbe5320dc4ecc73c15e2dd87b61969bd0581
docker~setup-buildx-action~ZABELH.dockerbuild
14.1 KB
sha256:8abd2648c4e270b1c73e67a0656f4d24190ea6a0895bf111e359318895a2dce8