Skip to content

feat(apply): safety hardening — atomicity, locking, pnpm CoW, sidecars, Maven gate #195

feat(apply): safety hardening — atomicity, locking, pnpm CoW, sidecars, Maven gate

feat(apply): safety hardening — atomicity, locking, pnpm CoW, sidecars, Maven gate #195

Triggered via pull request May 23, 2026 03:37
Status Failure
Total duration 17m 31s
Artifacts 38

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: e2e
coverage-merge
0s
coverage-merge
Fit to window
Zoom out
Zoom in

Annotations

9 errors, 13 warnings, and 1 notice
clippy
Process completed with exit code 101.
e2e-docker (maven)
Process completed with exit code 101.
e2e-docker (nuget)
Process completed with exit code 101.
coverage-docker (nuget)
Process completed with exit code 101.
coverage-docker (maven)
Process completed with exit code 101.
test (ubuntu-latest)
Process completed with exit code 101.
coverage
Process completed with exit code 101.
test (windows-latest)
Process completed with exit code 1.
test-release
Process completed with exit code 101.
dispatch-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage-docker (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage-docker (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage-docker (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage-docker (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage-docker (composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage-docker (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
SocketDev~socket-patch~15F6HN.dockerbuild
34 KB
sha256:ad66c584abd234b279fcfc016f7e8112b6a288b7510296c66e8926811ec550d3
SocketDev~socket-patch~1FEQDE.dockerbuild
11.3 KB
sha256:b4f153c4249d303c8148ea64371cd87bb1fbfc94f457878e6ab563d4d2452cb7
SocketDev~socket-patch~1YSHY3.dockerbuild
34 KB
sha256:204b31bbf354532bd940594315e5e2bededadef0eb70606574807d700add336c
SocketDev~socket-patch~2PWZUS.dockerbuild
11.8 KB
sha256:701689d43d6e4bceb4c7e8e5acec41ebb2baf7589a01df2a306fae9e7d680ce5
SocketDev~socket-patch~3UJEH0.dockerbuild
20.3 KB
sha256:4f987f4c676b88aa7da88b018fb0fe0683f97fda94248296f607b2df620331fa
SocketDev~socket-patch~4VLYRO.dockerbuild
33.3 KB
sha256:c8bdee637d217f181fed4477aeecf011ffbe12e034ad3f443fe87a714a83ffb0
SocketDev~socket-patch~6QUCQV.dockerbuild
33.7 KB
sha256:e8d1b4a6ef3294ddc8ad5cd79fbc555871bec8d95a3c8655f207d35810b54c3a
SocketDev~socket-patch~77EZNJ.dockerbuild
14.9 KB
sha256:805e794b312a4e865f8792b37ba0bd93ad5131a2dd2de67248859e305a52e681
SocketDev~socket-patch~8PQACT.dockerbuild
34.2 KB
sha256:742aa8044e208dfb30bf79a91df8195d75908ed01cad63cdcf81fcaf065650a8
SocketDev~socket-patch~AL1O12.dockerbuild
32.7 KB
sha256:b71a303dfa2417b41b3d30d111f2b9217e3573eb9a82160caf2b662ac0b9cb9a
SocketDev~socket-patch~CIQ01M.dockerbuild
18.7 KB
sha256:ec321ab3cf97ac4c1b852508efc2f3ad6a858feabd58a85a17f3e5ac7081dd18
SocketDev~socket-patch~ETBOKL.dockerbuild
33.9 KB
sha256:bbace825da45e70c5f3031d16cd4e18603099cd5ddc8b4b06020d53c1951e5f0
SocketDev~socket-patch~F34DBZ.dockerbuild
33.5 KB
sha256:a9f29a1ea842b13ca342a611c5aace447e0baf58455469f0b34861a27b43558d
SocketDev~socket-patch~FP75N5.dockerbuild
17.9 KB
sha256:5867c387f9589c8db06638b8ba543e01d6db3c912858fa26113e49111870c8ca
SocketDev~socket-patch~GULEP5.dockerbuild
18.4 KB
sha256:d79cbe43813d08281fbdea49d3998aafd7550e9d716c2458624ea49945c53615
SocketDev~socket-patch~H9IQMI.dockerbuild
34.6 KB
sha256:732570433da12f611ee29d105fef04117db00ad7ccef1a7a81c327bf979722a5
SocketDev~socket-patch~HYRJCE.dockerbuild
24.8 KB
sha256:582faa7a1b24e2ebf0df2e6e2d19730711790450ef4de41d87e1af4ccaebed91
SocketDev~socket-patch~IQFSFJ.dockerbuild
33.4 KB
sha256:d3ae16948059009d03d1b80f685f9f62e6c75ebca4001ae7785593cbdab693cb
SocketDev~socket-patch~JSKW6I.dockerbuild
21.1 KB
sha256:a883d33cc8b64964afc7e36fbc5c41c61d9751f81fff1148112694deaed0a9b0
SocketDev~socket-patch~LP76VJ.dockerbuild
34.3 KB
sha256:4165cbc1c333eaffe2edd9848cfe3df6efa056d8411a5f76fae81d26e50f6144
SocketDev~socket-patch~N0Q06N.dockerbuild
15.4 KB
sha256:df7c49324c89e797f0d649b4e7a399eff8e51e80f22b7667bb5f8b3f3804d2b3
SocketDev~socket-patch~NMERAB.dockerbuild
18.5 KB
sha256:92b87ed6a8847f1a0e2262e5abc3771a6011c16c9ed4f3b59ad03c991c175082
SocketDev~socket-patch~OBFZFC.dockerbuild
15.9 KB
sha256:5e0028d75854fc93ea65b76e0f94a43e2e0012161e7f06134e097ae8ad0fa4e2
SocketDev~socket-patch~QQWH3O.dockerbuild
33.8 KB
sha256:3f87b454f129646cf76c20d47be8d13af9ce4c6385138f4ccb5813f3cbbe5afe
SocketDev~socket-patch~WJ086R.dockerbuild
33.5 KB
sha256:dcd9237ed2188e00e2f2dd26f00354dc738f511e5e7ef49aa77d02e39c61a6c5
SocketDev~socket-patch~WZV7TP.dockerbuild
33.1 KB
sha256:68c248789ec4924390b7a803bd22254e3b9ebe49a61bdf199e6dc8b615008223
SocketDev~socket-patch~X1FQPY.dockerbuild
20.7 KB
sha256:73779e3ef589dee2158846dd93f390bf446d68c27aae1504661daf8242916151
SocketDev~socket-patch~XLO2MZ.dockerbuild
23.6 KB
sha256:c96f3d944974a12c34bf0b179856189496c7b2ecee2e6f95d5e660f9496f689f
SocketDev~socket-patch~YC7U9A.dockerbuild
33.4 KB
sha256:bfd95d7259c311a8ec92cdb0e27c9014b1bfc7597ce9a927996ac937627b20bb
SocketDev~socket-patch~YU6EYC.dockerbuild
21.9 KB
sha256:23187f3d699e683b3dda58cd3516cb2740bd060cb3b9d7f056d4430d4fe69024
SocketDev~socket-patch~ZI9ZYA.dockerbuild
33.3 KB
sha256:57647a8d23540f4c1bc0ea31889b4cac74ad43bc53110d57cfd577bd4a1fd91c
SocketDev~socket-patch~ZYBQC7.dockerbuild
17.5 KB
sha256:d3cb6ca46b831f2ca1dbf293e45e5cc2f4191b99a1bd1d20e36fc918cbeb68ee
coverage-docker-cargo
27.6 KB
sha256:d302db618e75bff8a3c18e954c90ee1709880c13e509083e398043bbe0b1ee62
coverage-docker-composer
27.6 KB
sha256:2720b5a71b4a1361c8837aecb47de3b006de4146bba1755f06b3073a4e85903e
coverage-docker-gem
27.6 KB
sha256:8c191064e52125d4d78c058b9695172229bbcaa7fc07bc688b2f6d69a476d87a
coverage-docker-golang
27.6 KB
sha256:0f6f8a8f9ac1859735fe00b0a81265e536a9992a2010581f05ced1d58f4b5dbe
coverage-docker-npm
27.6 KB
sha256:43a1bda4ecfe35922a950af9dba92b2dd9176187cc57204d5341f8b2bb51093b
coverage-docker-pypi
27.6 KB
sha256:bc83035936f3becdaea39d96761233335f4e6a11d5e0a5b2ae3af6704d5aa114