Skip to content

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

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

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

Triggered via pull request May 23, 2026 00:38
Status Failure
Total duration 9m 8s
Artifacts 39

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

6 errors, 13 warnings, and 1 notice
clippy
Process completed with exit code 101.
e2e-docker (nuget)
Process completed with exit code 101.
e2e-docker (maven)
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 (windows-latest)
Process completed with exit code 1.
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/
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/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 (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 (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 (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 (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 (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/
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/
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~1DLDRW.dockerbuild
32.9 KB
sha256:5e520a01db81da8570ae278346e44c069081b71fc63df78bf3793ad241c34d77
SocketDev~socket-patch~1PRTE8.dockerbuild
22.3 KB
sha256:b5647de575299ef33c8d78870766270905d341685eb51ae5e829d4b3aed1052e
SocketDev~socket-patch~2ETXR7.dockerbuild
34.5 KB
sha256:ad7cde2da56090d79b993ffcf0e0e0ecf1bffbcae67d81e92004a364da2a4d7d
SocketDev~socket-patch~3DS9OP.dockerbuild
33.7 KB
sha256:e4cb293986a39a33561b37858261c5aad8cd7ab7dfce8d15bb82d31cec413440
SocketDev~socket-patch~6GE74O.dockerbuild
24.5 KB
sha256:57d8ea7e1a903d0744ff0cdca18da4ace9be0a9226f661d245ca3b36fb253827
SocketDev~socket-patch~88XCUY.dockerbuild
33.4 KB
sha256:ea33b7281d21355284f312955d104e0057e3e2e62b18b5efe9853516c02f1b3f
SocketDev~socket-patch~9LF9ZS.dockerbuild
18.7 KB
sha256:46d8478bc1b6c95c77be418eb818bc9e0be5737b24b11b1e1759f7347b6f33be
SocketDev~socket-patch~BQ2M9K.dockerbuild
11.2 KB
sha256:355c304509762eb953245e2d33e9e1f52959904c63ca3b8f3f24c327660126dc
SocketDev~socket-patch~BWSKD5.dockerbuild
33.2 KB
sha256:a666854fe3171a4052c4dda60f148f500054e8088c31e1aea84152d9ed18ccf3
SocketDev~socket-patch~EQYHK5.dockerbuild
14.7 KB
sha256:e59199d8b711a345598fd8aba154d0c349d202383a68f357c8335453e9f0f19c
SocketDev~socket-patch~HFOFEG.dockerbuild
17.4 KB
sha256:fe9420b92da4ef259da12401bf281a97c4aadc00408923780bb1f5ff72412111
SocketDev~socket-patch~HKV2K1.dockerbuild
34 KB
sha256:5cbc415b98e114e90785f7b3f8cf4b8964c83d811f76dd7164318ea047aeb076
SocketDev~socket-patch~J227P4.dockerbuild
19.9 KB
sha256:9db89fa0ebe0c8328b6032a97a0ce86237406922c8519e79b119eecbdc0db830
SocketDev~socket-patch~KYQL02.dockerbuild
33.1 KB
sha256:5ab58b856c681b19f53c354d4f7538d9a2af41673f7bd6e784426dd70a1b4e26
SocketDev~socket-patch~L3BBXJ.dockerbuild
33.5 KB
sha256:0b6245dc15aa7423d7b43a0a2950c599396f14561818fc0642e97df4b5a7368c
SocketDev~socket-patch~MKSZK8.dockerbuild
11.6 KB
sha256:a06a8a4a77074bc2c8136e213dfcefd5c0bcbcc51ef40f59aa14e43ad726da0e
SocketDev~socket-patch~MMNRZI.dockerbuild
33.9 KB
sha256:a5cb42513ce812eaf85dbc1c9a6ac3f27793ea3095f887ec13803df467dce940
SocketDev~socket-patch~PBIRGN.dockerbuild
33.9 KB
sha256:f968b883887cbaf57c2d2162565c357c63ef3050b8f7991fcdd1f5b147edda86
SocketDev~socket-patch~Q5TONG.dockerbuild
17.5 KB
sha256:8aa5a87b0b57f0de1ab71c39bc61bb66195e062b90207b124e562e129b8dc23d
SocketDev~socket-patch~QOFXKR.dockerbuild
21.4 KB
sha256:8f4f01d2a739a450815c12f276012d6a3da4b0156ba1511b7d377ec3659c0e1d
SocketDev~socket-patch~QU9F9G.dockerbuild
18 KB
sha256:a3ff9bdd0fe4293e4898076a7b3f4cb9fed04007c985e09bc86f07747a097d9a
SocketDev~socket-patch~RLKVD5.dockerbuild
17.4 KB
sha256:a273f7a84bd007eb0e3f1fb19b31f0271c869e9f19cbd48cc480302e15edf477
SocketDev~socket-patch~RZS9G5.dockerbuild
15.7 KB
sha256:efc842b82b67dfc14e09b6100251c9aa6ffe09ba96329925bfc0bc3ac000b03a
SocketDev~socket-patch~SRDLXN.dockerbuild
19.8 KB
sha256:61c10d8616677ecb35acc7d52b1661454ae83524154d3b94110cc2718f77299d
SocketDev~socket-patch~THCHAA.dockerbuild
33.8 KB
sha256:8f63ab847b4db1e4c453552e258bae1e092f7fe4cf00eb2d991ea244032bbb59
SocketDev~socket-patch~TLLECZ.dockerbuild
24.3 KB
sha256:93aed53dc916172499a34d024ed3bc8fac4291811b4ef67b5d44d4eaab584d63
SocketDev~socket-patch~VEDZEL.dockerbuild
34.2 KB
sha256:b2cc2ca0231506c7ae149763d4482b93764a2ae1ba94ab9caaa38c6194d64530
SocketDev~socket-patch~VQWPHA.dockerbuild
33.6 KB
sha256:19830f9864fb77295436af11cabbb52919757752d237d2ee2a657a3af8840337
SocketDev~socket-patch~Y7YU5L.dockerbuild
32.9 KB
sha256:1781acd93668e211706dd0c9a01114bda9a120f68a17755aef5cfd04fd48fbb5
SocketDev~socket-patch~Z2I7GG.dockerbuild
34.2 KB
sha256:0e20d0b38221107697f1917f4a4ef91eb0094eab5ba6b98e3a61d4422da8a5c2
SocketDev~socket-patch~ZNCQEF.dockerbuild
33.6 KB
sha256:73349521023275663ee069d7d21a09d3268762f7318297ebe44689cc3db18c4e
SocketDev~socket-patch~ZWS5DP.dockerbuild
18.8 KB
sha256:88950ebbc632ee6880f1d78e90b1092a2fa08b96570942c633f8f94daa8481e1
coverage-docker-cargo
27.6 KB
sha256:e7d9daa5cad6c304fb04c10da87abe7eff9af8b64d51760d1ef111f95a4834b1
coverage-docker-composer
27.6 KB
sha256:2ce787bc5fb6175a91e9691444a036320b068f1194188af80267ccbd8f33ecba
coverage-docker-gem
27.6 KB
sha256:df87f2879c6d579d1e4a5cac0cdd9536ededa1cb543531eaadd542f340f5cbea
coverage-docker-golang
27.6 KB
sha256:558c7186190282dc6247ee5abfb8dcb4bb2fe96b14ee008d01cd394f424e5467
coverage-docker-npm
27.6 KB
sha256:96109f64dc7cdded245763c81cda09d9a3153665c1b4a82c7b6316428e9c2546
coverage-docker-pypi
27.6 KB
sha256:5144922b56c527a4282ced314af6dafa64bf131df6fa7dcb32a7d4e551086c53
coverage-host
133 KB
sha256:909fd537f2cb6a4115620de8b711d33c1ab8abe3a53aff591559e07798e4d46e