Skip to content

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

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

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

Triggered via pull request May 22, 2026 15:43
Status Failure
Total duration 9m 54s
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
coverage
Process completed with exit code 101.
test (macos-latest)
Process completed with exit code 101.
e2e-docker (nuget)
Process completed with exit code 101.
test (ubuntu-latest)
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.
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
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/
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/
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-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 (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 (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 (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/
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~018H16.dockerbuild
20.9 KB
sha256:b050a428122fb4d41cdb9a556707a7b3e54a20b4a281f9d8c1a110441cbf439a
SocketDev~socket-patch~3MLS8G.dockerbuild
17 KB
sha256:37db1c246c0f54d9e08b05a4d840402e56a12f66d84ba399ab8f3b6f12860841
SocketDev~socket-patch~4SA83A.dockerbuild
34.1 KB
sha256:2916a18b20f1811bb541c1b48d8c2013a3390849766b08f211856af0aedb153d
SocketDev~socket-patch~684B8W.dockerbuild
18.4 KB
sha256:00ae695d6682324d6153605101368972d71d36d6b28c6028c68750b9afca5fbe
SocketDev~socket-patch~C3UZCH.dockerbuild
21.7 KB
sha256:bb937d477862b9104b18c23aa1d1a8547e30ed616b3011047e239f2c3ebacf7a
SocketDev~socket-patch~DJBH54.dockerbuild
33.5 KB
sha256:97d53a372bd47e1ee38eb01184414f1b6c9b112947f68a86d5c05e65d8e8782b
SocketDev~socket-patch~FK5GFN.dockerbuild
18 KB
sha256:25eb5662f9a88b13986bdd000e612ce005aa405c46c753327a4427f1c51f33b4
SocketDev~socket-patch~FUZGKQ.dockerbuild
21.5 KB
sha256:b67f76e064da0365c1767d7c6d4b1fa6eb7e3ae3ae6a54cf133baf9b73afffda
SocketDev~socket-patch~GL7DPY.dockerbuild
32.8 KB
sha256:554df7703d94cb7e7958071ab1ea36b1f4522f5f86845f44c4e0b937b437e750
SocketDev~socket-patch~IB0SE9.dockerbuild
11.4 KB
sha256:9ca0279789dd9209933c3b20b86c6543188cf5d3149aba56ebca172a212d7e75
SocketDev~socket-patch~K1PO1I.dockerbuild
33.9 KB
sha256:1fa46947c930ab779c45b53d1683f9506c2ebe903198ab50010b7bf8584178b7
SocketDev~socket-patch~K2C42Y.dockerbuild
33.2 KB
sha256:1cf1a63fb46cfa7d8b746fc94d1ba2a0361123a8b5db21b2271de2d75ccd48aa
SocketDev~socket-patch~KOHUU2.dockerbuild
20.5 KB
sha256:161e10d4450222e8d69dbca024cae164a469d5003429e680b22c81a45a4c1fbf
SocketDev~socket-patch~L29E5I.dockerbuild
14.8 KB
sha256:be7fe0d7555707ef91f115ff089817d0507c1ddd67022ec68acbfc79cadc6127
SocketDev~socket-patch~L2I1M6.dockerbuild
11.5 KB
sha256:23216914d96fd50291a1c464aec4c01b7e500e71db4f47b43b713333009be4f1
SocketDev~socket-patch~L3SBNO.dockerbuild
32.6 KB
sha256:1b87fb2e93214c37ea94912b9a8fe23e92eb736ee1f6947b8bed76ea51013657
SocketDev~socket-patch~L8F6I2.dockerbuild
33.1 KB
sha256:2f734ee165a2e944337db77ccd843d4cb230f4f85504a53039cd5d70b3314849
SocketDev~socket-patch~MAA1JH.dockerbuild
33.9 KB
sha256:b9e4a315a39e1dc2c10d66f96930d7173eb056a9f2ee5926897c5fba43980dc0
SocketDev~socket-patch~MFNIYK.dockerbuild
33.6 KB
sha256:d78cffe578427a516985181a507429a3d1cfe5c0403cc778affd9009f596ca65
SocketDev~socket-patch~MLOGFS.dockerbuild
32.7 KB
sha256:339a47ae9522446db6f73572861c44e54c9e0ae0d56c592ddfd157cd9dcc5474
SocketDev~socket-patch~MQMK3H.dockerbuild
33.4 KB
sha256:6625d7fbe677d06b4d6d45de1c223b5327dc58033504dc50fa219d8c11bdcb88
SocketDev~socket-patch~NUXCMA.dockerbuild
33.5 KB
sha256:83b5d33d4a7477b05287eaa685d5a575da008a35b0c5e9c1a8eace5f14496523
SocketDev~socket-patch~OJVV95.dockerbuild
32.7 KB
sha256:4404d4cea09a1012988af706603e93397ae171cee62ed6a32e689a2b16ca291a
SocketDev~socket-patch~OKYH94.dockerbuild
17.8 KB
sha256:b43f9112433ff149f05ecc972a430854eba37c8f1d7d5c375386a36d536b5a93
SocketDev~socket-patch~P7D5ZE.dockerbuild
15.9 KB
sha256:57c9c1008df5b785d1af46185cf5a7680c64651d19575d03976be2010233f155
SocketDev~socket-patch~UEBCH9.dockerbuild
18.6 KB
sha256:61a435cf5dc33055296be47d0bbe220f3d736d2b8de4c66e3fc2dcb850b221bb
SocketDev~socket-patch~VHR2GH.dockerbuild
34.4 KB
sha256:d86cc8a9b7e9d4478514898f4b28e5cf0d0b29f6a6c8404ed26bb52e3b884e44
SocketDev~socket-patch~WOXWI3.dockerbuild
23.8 KB
sha256:099385640a9a79374886a8603877b28af8a69173d00243e91aaa4b753fc89850
SocketDev~socket-patch~WQD3RN.dockerbuild
33.8 KB
sha256:f7d9188413cd6a6e0bce365f87bf073c9318edf96c4bc60ec06445ff6a5dd5fb
SocketDev~socket-patch~XDRUP6.dockerbuild
33.8 KB
sha256:66963359814244ec92b6fa3ee935dbdcca6f69e7a2e8ed944f3d54abd8397873
SocketDev~socket-patch~XJ67SK.dockerbuild
24.1 KB
sha256:7acae82bbd4ee765643cda82c20d75dc66b56dc2fbe70486a5f3f39e3b55e6d7
SocketDev~socket-patch~ZCJ1WB.dockerbuild
18.6 KB
sha256:20885569e142c442352ba0dfce24f3149828e742a6c18b1d5a5a952eba2663db
coverage-docker-cargo
28.6 KB
sha256:9176dc8541383a0121d68647a885a791641784173b2dc4983f6780117b9c3c78
coverage-docker-composer
28.6 KB
sha256:2f520b263cb9d771f5d5cb41fa60980911a636e49f40f219c8d11e323f1e1d0a
coverage-docker-gem
28.6 KB
sha256:10fb9e55feabf30bc285d45581db2deb16baea9c95e51817848a325a38f3c3fa
coverage-docker-golang
28.6 KB
sha256:a80f65fa2bc28a8367de871d109422be9971058c72f4234023520d60af578078
coverage-docker-npm
28.6 KB
sha256:c5d6f01c3395d8ba5f5d2fc12fa1ee8b2f80bef1f59670f631ce38a84978bc0c
coverage-docker-pypi
28.6 KB
sha256:afd23e54aae60e5b83415e9257e6b1378d2e71dbfc970fd14d88b7f06856bf7f