Skip to content

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

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

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

Triggered via pull request May 23, 2026 03:10
Status Failure
Total duration 11m 39s
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 (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 (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/
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 (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/
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 (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 (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
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~0WP6GO.dockerbuild
34.1 KB
sha256:4f021224b761cb8ac639ea12f7788169a4e432280a7c12ceaa40e2f782bc354f
SocketDev~socket-patch~2S08I0.dockerbuild
33.4 KB
sha256:6891a5f16558c2fa00d7b11e9d6f91cedf8bd012d50d0e250d41f6c3de12a4f8
SocketDev~socket-patch~35FBR8.dockerbuild
33.9 KB
sha256:9698d0c5820b96ead9acfb7a8e583676e5a6145888d1152b876bba40cce03694
SocketDev~socket-patch~3GK2AU.dockerbuild
23.8 KB
sha256:60a04acfb000287109fb9c604ef64f4379603dcad085115fcc9735f13b0a80ef
SocketDev~socket-patch~5NPOTF.dockerbuild
32.8 KB
sha256:077183ca31a1ee5e1bf6ffe5e40a99036669ce51fd3a9c439cc64071778e7da0
SocketDev~socket-patch~6QJCPV.dockerbuild
14.8 KB
sha256:c18acd997bdcf4298a3f59e979624c10dc901d3f22af33c197523c03800e0ec3
SocketDev~socket-patch~6UQCD1.dockerbuild
33.4 KB
sha256:52c5d2e12b9a287cc4de8b734ed96ff76d247c6b08cad5e4d90d5127c1d4c76c
SocketDev~socket-patch~7YSZNY.dockerbuild
18.1 KB
sha256:da8e6d26bb798274d72a627b15afcd1273fce3004f7c8b803240f6ee9ba18b86
SocketDev~socket-patch~8BV8P2.dockerbuild
33.7 KB
sha256:a49fd48a963eebacd5759e49ca9a21585a2796ca1113d5dbee4a04c263c62ec0
SocketDev~socket-patch~8PJVDY.dockerbuild
32.9 KB
sha256:91eb544b0cedea3749e2bf331f3af0fb7dc8c3ee03592aed53f4b7c700d025a5
SocketDev~socket-patch~9HDVVZ.dockerbuild
33.9 KB
sha256:5b4d6e20b71460bddfd157126a1bc800cbc94c1578ff2a2cd9ad44f63d68b9f1
SocketDev~socket-patch~C77VZB.dockerbuild
20.7 KB
sha256:9d7e02959b9501db873dc10dc5ae42b9f9555c398ef1b5a7c742a0eac283c21a
SocketDev~socket-patch~C7JY80.dockerbuild
33.5 KB
sha256:a3fdf051b1d56ca2d55947f532b31694d902fdbbd307809b47442384024c8898
SocketDev~socket-patch~EMXUQ7.dockerbuild
33.9 KB
sha256:95efa7c44196bdd1b2cec2bedbea0dd766a378c6c1fe22f4aa9c0f12c6a461d1
SocketDev~socket-patch~IH4Q2U.dockerbuild
33.3 KB
sha256:58adb3597cd7f62a6cc4719ce929bae04cb43d592c236242627285a9a7d36460
SocketDev~socket-patch~IXTS3R.dockerbuild
33.8 KB
sha256:6a27ae575fcea891f56e0ee2f156508733e2b53fa316a5a97bf53f3aac5de6b9
SocketDev~socket-patch~JJVB8C.dockerbuild
18.6 KB
sha256:f692b75f68d52e4ff386f60761b24aeea2fe35dbc638555f1d0e86a07d0bf9ce
SocketDev~socket-patch~JN1IES.dockerbuild
24 KB
sha256:a8881e392f0c1a43f1dcfe14d00eb03dd52d3cc2b92613f7e0e702d7a117f900
SocketDev~socket-patch~JTIXVY.dockerbuild
33.7 KB
sha256:d3adb8673107d8eee25607a47ad00f1d66a0703b900c032663fdef1c930c23d5
SocketDev~socket-patch~KIEX5M.dockerbuild
34.4 KB
sha256:86202be1a4f40b0d5f51f122328e8330a5e17f7eb7f9dd8f393dab6f986e824d
SocketDev~socket-patch~KUQRWI.dockerbuild
16.1 KB
sha256:f7c6abee7a676fb14b5345e88ac4eefcb9ae3a94d24cab3f40452ab6e34c743d
SocketDev~socket-patch~MTN4W3.dockerbuild
18.5 KB
sha256:6e3024f0dbbf87c8c3c11c5c60ea28a2ce22d8dafb93e149ed0593e51a9feb8f
SocketDev~socket-patch~MUDOJI.dockerbuild
17.8 KB
sha256:77f05be957e5b9c8cb70538d30ae51b2996483ab406d2e6760e3be7f27c42d02
SocketDev~socket-patch~O2K2Q9.dockerbuild
15 KB
sha256:f2b66f6c20dd2b5fec4e95c4c3958a26d6b2e61e6ff75af549b7995facf4dcf0
SocketDev~socket-patch~O5EH8O.dockerbuild
21 KB
sha256:52d8ebbc2fa0903982c4ac2aafd2dcdd148a77ccd2d37fda978273d913795c64
SocketDev~socket-patch~P18S0L.dockerbuild
11.2 KB
sha256:137da22777873576f69b8ec17c9636c5227125848823e8aee48f1fc8b8c522ea
SocketDev~socket-patch~Q7ILY4.dockerbuild
33.6 KB
sha256:35b68221b784c1f277167881d7ec84b244f1db6681645132f232b704be8358e1
SocketDev~socket-patch~R6PVKJ.dockerbuild
21.8 KB
sha256:38f0c4acf39859cde15522b897e7238d5de38b373d09fce65b133168cde10d02
SocketDev~socket-patch~RFFUKN.dockerbuild
22.2 KB
sha256:5264eb86136ec8be6924e205233de956bb7ddfbcd9cca67247ed7ebeec061b5f
SocketDev~socket-patch~U0DERH.dockerbuild
15.9 KB
sha256:79062fbf6490ac90ce1e5d681c420c223abd18965377469abb70da5ba0681061
SocketDev~socket-patch~U5Q7OY.dockerbuild
33.1 KB
sha256:fd47d5bccbfcb2d1b44afff2da282268c508bb5a2eb00337ff1293d1ccad17a4
SocketDev~socket-patch~WKJPS9.dockerbuild
11.8 KB
sha256:374ada020d231b0ceed3297809658aadffd61897053db5776c563ace7691d4a0
coverage-docker-cargo
27.6 KB
sha256:8b645c87f8eb76d9a6b391288d9ad3a9e4eb4c9a65ce4e6695a13f0815c82904
coverage-docker-composer
27.6 KB
sha256:f362cdea08c931826a16d723e5df5340dddc6299f4ef8ad45f4b2f8f167948b0
coverage-docker-gem
27.6 KB
sha256:61848f7feae86c92e3db0f652f1ab9caa85f2c8b670ea3076ab178e8966a651f
coverage-docker-golang
27.6 KB
sha256:d3f8f5921144a57b631ac0a334a7d6c3036d8ee2118d04bef09e0c2e52b7a94e
coverage-docker-npm
27.6 KB
sha256:728033fe255b8dcfb1494a6792167844429ec024b4d7196966d72e9d0bab035c
coverage-docker-pypi
27.6 KB
sha256:c92362b894d41a9fbb45833049e99383f9dcbfab4e116f97145038c76b501be4