Skip to content

build(deps): bump crazy-max/.github from 1.0.0 to 1.10.0 #240

build(deps): bump crazy-max/.github from 1.0.0 to 1.10.0

build(deps): bump crazy-max/.github from 1.0.0 to 1.10.0 #240

Triggered via pull request June 5, 2026 09:23
Status Failure
Total duration 45m 24s
Artifacts 25

test-os.yml

on: pull_request
Matrix: build
Matrix: sandbox-build
test-freebsd-amd64
3m 4s
test-freebsd-amd64
Matrix: test-windows-amd64
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 21 warnings
test-freebsd-amd64
Process completed with exit code 1.
test-freebsd-amd64
Process completed with exit code 1.
test-freebsd-amd64
Process completed with exit code 1.
test-windows-amd64 (windows-2022, containerd, ./solver)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./client#3-4)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#12-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./worker/containerd)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./client#4-4)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./cmd/buildctl)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#11-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#1-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./client#2-4)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#2-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./client#1-4)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#3-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#4-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#5-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#6-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#7-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#8-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./..., 1)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#9-12)
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 16th, 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-windows-amd64 (windows-2022, containerd, ./frontend/dockerfile#10-12)
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 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
buildkit-freebsd-amd64 Expired
79 MB
sha256:11eccfc782137ca108a26dc032c9ca6ce3b5b82062b27fd38d0ba225cc1f13a3
buildkit-windows-amd64 Expired
103 MB
sha256:a604d19c2a116c3cb48404a5333cdb83345b281623846e9ca0ca1fbe25b9a62e
data-accelerator~buildkit~H6609X.dockerbuild
76.1 KB
sha256:3d2907894920ba9c352b2a5b83fc5522779053980ff6618cc02507cad9200238
data-accelerator~buildkit~WZUX77.dockerbuild
74.6 KB
sha256:76a9bed7dc6326487f0f17655bb14a3637d08a93e5a11c12c33e8e5568bb978f
test-reports-windows-2022-test-windows-amd64--1-containerd Expired
423 KB
sha256:9a53d00e364839be584ffae71921d2d2ad015c46b05f7fe537aa8d0f90064939
test-reports-windows-2022-test-windows-amd64-client1-4--containerd Expired
12.3 KB
sha256:3e787381a1a0e4ae76928d5df5ae46867f517935ff216976e477bb704dc01d62
test-reports-windows-2022-test-windows-amd64-client2-4--containerd Expired
12.2 KB
sha256:b50bec8f75648eac3879eb8ab4a6bd7b1888c7f3e9b2640e9b9dfcee97de264a
test-reports-windows-2022-test-windows-amd64-client3-4--containerd Expired
11.8 KB
sha256:727ca3dccf260a598f2cf202ea53b51b6dae8fd2377582a3540fd67cde176492
test-reports-windows-2022-test-windows-amd64-client4-4--containerd Expired
9.89 KB
sha256:34f301b8624cba1a96d8153b2c5bc90b31df55df846511dbfab9a5db7e289219
test-reports-windows-2022-test-windows-amd64-cmdbuildctl--containerd Expired
3.65 KB
sha256:20a76b99d803e1186504c582395e7b611366804ad1b00efc7fa6e148c0494ce7
test-reports-windows-2022-test-windows-amd64-frontend--containerd Expired
1.14 KB
sha256:18ff39bdf8104fe2a762443c63c7e199afb5b8276e099aa6b0dc4e51fc926a19
test-reports-windows-2022-test-windows-amd64-frontenddockerfile1-12--containerd Expired
9.23 KB
sha256:f98a2759c0e0f8fcbf0e73dade875a82198b005171d0ba6a3f968e47278c432d
test-reports-windows-2022-test-windows-amd64-frontenddockerfile10-12--containerd Expired
8.29 KB
sha256:1eed17a63af55ee48f2287b3bdb11b76215bb95a69137fab82d6adf4a0cd6bc0
test-reports-windows-2022-test-windows-amd64-frontenddockerfile11-12--containerd Expired
8.23 KB
sha256:a3862efdf65705ad8f0de6a82e61f79e53fd4286a127bd5685aa0310a49bc134
test-reports-windows-2022-test-windows-amd64-frontenddockerfile12-12--containerd Expired
4.36 KB
sha256:530f43031c0601632f540d6e94e05cf528a5321e3d5a9cc59b4a5ffa8b8081d7
test-reports-windows-2022-test-windows-amd64-frontenddockerfile2-12--containerd Expired
9.11 KB
sha256:70de5c5ee2b685dcccb351530683ec5ed9de4834aa7bb8dbdeee31e226806ef3
test-reports-windows-2022-test-windows-amd64-frontenddockerfile3-12--containerd Expired
7.46 KB
sha256:967cedefdbd8e8a059a22bf1752b98aa78f22ade6ddece748b9b5234f134c0ae
test-reports-windows-2022-test-windows-amd64-frontenddockerfile4-12--containerd Expired
10.5 KB
sha256:7ac0f0e7ba12b5fff21f2d441e4b92069815fc713da0ae68671e34ebacd3eac9
test-reports-windows-2022-test-windows-amd64-frontenddockerfile5-12--containerd Expired
8.94 KB
sha256:1147ce10769d2e92676f1305d24cc22215245097b58a2c5890f200c4a1419c26
test-reports-windows-2022-test-windows-amd64-frontenddockerfile6-12--containerd Expired
8.47 KB
sha256:2ef1ed0e5daf71989616018005543911b342bc9557c644707edc7046d40f7878
test-reports-windows-2022-test-windows-amd64-frontenddockerfile7-12--containerd Expired
7.52 KB
sha256:e8dec0942d24e054f9ff9a6f37afb7431b98533a5599a731ad5e50d5414996be
test-reports-windows-2022-test-windows-amd64-frontenddockerfile8-12--containerd Expired
5.82 KB
sha256:40d15a35a2b3c4d630391479d3eb7befef1843bfa9c9920c1544d36052c5e4c8
test-reports-windows-2022-test-windows-amd64-frontenddockerfile9-12--containerd Expired
7.99 KB
sha256:ab4cf3bafdd5d2ee3b2004837653606254ecdace0f4286e540524ceb4b1b71b4
test-reports-windows-2022-test-windows-amd64-solver--containerd Expired
12.9 KB
sha256:f983ef35d7241c84cc1e3ce263e4f9413e20384ffb0070930569e5b002cdf84c
test-reports-windows-2022-test-windows-amd64-workercontainerd--containerd Expired
1.38 KB
sha256:67729e84e0941ac376f0927d655a95edc5551253a00c9bd0019528d25dd63f3d