Merge pull request #6586 from moby/dependabot/github_actions/softprop… #8568
crazy-maxtest-os.yml
on: push
Matrix: build
Matrix: sandbox-build
test-freebsd-amd64
2m 51s
Matrix: test-windows-amd64
Annotations
22 warnings
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
test-freebsd-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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/
|
|
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 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 | |
|---|---|---|---|
|
buildkit-freebsd-amd64
Expired
|
78.9 MB |
sha256:094a9bf72ca976983f6185674e3ece9933a6eb0b9bcea1736f16ee4879da901c
|
|
|
buildkit-windows-amd64
Expired
|
103 MB |
sha256:ef406339077dc535afdde1886845b517dab8ba9c4f23efad0ace60c7a93158b4
|
|
|
moby~buildkit~IJ09U0.dockerbuild
|
209 KB |
sha256:18546dd6e341a7db99302ee3d935109a16bafe17fee71daae249d0e5a1dff5ab
|
|
|
moby~buildkit~JAW4FE.dockerbuild
|
69.5 KB |
sha256:2c9306ca318d15e53bd3fa55aaaf7a27433b32d67d2927a59f8065414b7f273e
|
|
|
moby~buildkit~WSTAU9.dockerbuild
|
69.8 KB |
sha256:303e42a1c72044ff98f280e0f6ebb4ed3d2f079415bc138704497740441f4b26
|
|
|
moby~buildkit~X4XR65.dockerbuild
|
207 KB |
sha256:401aa39271151780b30d3389eefc2edd4590942d52a99df46d1b7e8ebb901bd8
|
|
|
test-reports-windows-2022-test-windows-amd64--1-containerd
Expired
|
423 KB |
sha256:1a7477340f387e2972bcbcd4494fc406d1331c99585e878f98fbfaccb357631b
|
|
|
test-reports-windows-2022-test-windows-amd64-client1-4--containerd
Expired
|
12.2 KB |
sha256:60ae0406d7287c2a540c2f20c0e6954e0f03e351542d6dd6ec582714f007ef28
|
|
|
test-reports-windows-2022-test-windows-amd64-client2-4--containerd
Expired
|
11.9 KB |
sha256:15ad6d05efa77f668e5b119f79c485a17eb06ac7833581a792fc8e995d0ac33c
|
|
|
test-reports-windows-2022-test-windows-amd64-client3-4--containerd
Expired
|
11.8 KB |
sha256:08a9a638664b53090a3ecab2f6c6eb7b7394c13a034da41be6ede07da8beb610
|
|
|
test-reports-windows-2022-test-windows-amd64-client4-4--containerd
Expired
|
10.1 KB |
sha256:f82e8d8da1d33885e48d8ecf1349aad5d05deb283213328707f94ab5c7e93f53
|
|
|
test-reports-windows-2022-test-windows-amd64-cmdbuildctl--containerd
Expired
|
3.65 KB |
sha256:3aeb67a31eda9fc5c995704b819a85386386127447ebe06812a41301d6da6c86
|
|
|
test-reports-windows-2022-test-windows-amd64-frontend--containerd
Expired
|
1.15 KB |
sha256:0f2667945727ecc40e4aeaa1b9974932c0cb305055b7eb9cde1f5091a6fd3b03
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile1-12--containerd
Expired
|
9.17 KB |
sha256:29875af3b019ebadf30b6331f6af23b2b034b220687b4e49885f8306fea53586
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile10-12--containerd
Expired
|
8.19 KB |
sha256:1ab04da0d9306d8b16485da7002a6c1928ff94217511d6cf89072f90e1f9d631
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile11-12--containerd
Expired
|
8.3 KB |
sha256:688f4d0f5ffbf2fa8658f3b707181a75364e2d9dbdd0b32379a62c6c2564f2aa
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile12-12--containerd
Expired
|
4.28 KB |
sha256:edb939be0b16402baddf82ea7843a06a709991fadc32e87b94875976f79568ee
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile2-12--containerd
Expired
|
9.24 KB |
sha256:92fca05148ff4b3d78af8b177719e923b0cb25a70c78bd65abcc297bddebb3e1
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile3-12--containerd
Expired
|
7.47 KB |
sha256:701885127275315177b95e8d6bd08d39303289d698cecfe2148ac2be568e6906
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile4-12--containerd
Expired
|
10.5 KB |
sha256:69b7992e727bac6628000de6b511bbc3494063eadead340303fdce7c1b52304a
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile5-12--containerd
Expired
|
8.8 KB |
sha256:5c87e75d7f5da2a5914e59aebcdf6127a23f28de05d200aa68e60bf891e2cd0d
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile6-12--containerd
Expired
|
8.5 KB |
sha256:b4ce17833b39e1fec28bc73ed6d42182769eedbcb9677abbfb398783c161147e
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile7-12--containerd
Expired
|
7.49 KB |
sha256:554a5fa9dfc7025664c6f7909e3ef644cc2de5a88d0ab22ababbb8246f87cd6b
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile8-12--containerd
Expired
|
5.76 KB |
sha256:4d5da862e241120a58478f696dbfbdb4f5cd82447da25dd1b933d87542efec2f
|
|
|
test-reports-windows-2022-test-windows-amd64-frontenddockerfile9-12--containerd
Expired
|
8 KB |
sha256:015d56e955e26e0fc144dd38ef77b32a2ae5a555ab133e0b18b3f008aeb6dad6
|
|
|
test-reports-windows-2022-test-windows-amd64-solver--containerd
Expired
|
12.9 KB |
sha256:af08e327a7fe1c69a7ef42d4d9fe08b159061cb65523cee56ffc89510f816861
|
|
|
test-reports-windows-2022-test-windows-amd64-workercontainerd--containerd
Expired
|
1.38 KB |
sha256:0dfb68d6ca7e676dbc39171cde1c759a7d46b1f3bc2a2dca69906c7a2daaab97
|
|