Skip to content

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

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

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

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

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: e2e
coverage-merge
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.
test (windows-latest)
Process completed with exit code 1.
coverage-docker (maven)
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 (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/
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 (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 (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/
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/
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~0VIEIH.dockerbuild
18.5 KB
sha256:fa83841028f14ae6d753a613d4df8d15703a0cdba9c2fa22c8abcacd15fd0009
SocketDev~socket-patch~16124M.dockerbuild
33.5 KB
sha256:87845e8168cf82366f8e6069f6f01d3063b253bc05a0d38af263eb540d23c477
SocketDev~socket-patch~2XK9Y0.dockerbuild
23.8 KB
sha256:70d2d13d0e914f1dda0196f0fef139285c92268ec5414b3b9739a6de266688d8
SocketDev~socket-patch~4JYG63.dockerbuild
23.6 KB
sha256:be136fb990960aee4255ee8a9a5615d69f4dc0b76dfcbce28ea821ca0862d38e
SocketDev~socket-patch~8KBXIE.dockerbuild
15.2 KB
sha256:cef48bb7739ddc4514bf1be519316264726316e02c49f68ff65aa330eebeffce
SocketDev~socket-patch~8MZZP1.dockerbuild
34 KB
sha256:2f7f21520f915aeb912c063e1e7af9af50e0dfbcd5fa4813a90af5511000062e
SocketDev~socket-patch~A2727E.dockerbuild
11 KB
sha256:4bfc5d644f51d37e768030eccbf741761516ec9991d9ed47cf0bb658a3b0e6d5
SocketDev~socket-patch~A4HYDR.dockerbuild
18 KB
sha256:d773f1bdabfb7952ff855efa225b508bee629040f5a387be23876aa128050d05
SocketDev~socket-patch~BG6SLT.dockerbuild
15.5 KB
sha256:edc8a2bf3448c2e7c18448577f5b713d87c4f91a73646c525e21febe2cb94ccd
SocketDev~socket-patch~D4E4HT.dockerbuild
10.8 KB
sha256:9e158dee23a85732503bc6853402179dc5d337f9b54bde2575dfd1cb81efdd57
SocketDev~socket-patch~DBKJ72.dockerbuild
33.8 KB
sha256:4510b9d28558b4b3d7f308d8cd589ba7122b65ed7cac3dd78698661798d2ffa9
SocketDev~socket-patch~DGV8HO.dockerbuild
34.6 KB
sha256:572ede808e7e159b9b45efb0bb7aa3498e9261c117660551d3b0a02df69c8157
SocketDev~socket-patch~DPGQSL.dockerbuild
32.8 KB
sha256:5c670d5c7dcc9fbb9b61fe114b5eddc7006275635ac750e11652c61cd6781296
SocketDev~socket-patch~KL0A0B.dockerbuild
33.7 KB
sha256:08242cda9cf373db7dd609b9e4109e41fdd029af7250721ecc7f05e8ae051e2f
SocketDev~socket-patch~LHZSGK.dockerbuild
21.7 KB
sha256:16f5942b8aa51e138284a454d68228c4545be54a569351a216cd0ea264bbffb8
SocketDev~socket-patch~LISCW1.dockerbuild
33.7 KB
sha256:af68da673e9b08bf930e55a7d5185552b502226fd797f8c0297b0ef74149f805
SocketDev~socket-patch~O0BFK2.dockerbuild
33.9 KB
sha256:1fe1f09cbd63d201b350a99be3734a1905b7d5054b7881dc70062c64aff4f3a7
SocketDev~socket-patch~R48ZC7.dockerbuild
18.3 KB
sha256:c726210070317fdae47c2bbd2745b6c047ba9a8fb3f55af77a123acf9626aa29
SocketDev~socket-patch~R7G2ZI.dockerbuild
33.3 KB
sha256:531fc714798b5fa858557fc49bd19f16d4943732c8a0c9a939d3549823b54d4d
SocketDev~socket-patch~RK0CYL.dockerbuild
19.8 KB
sha256:13a516bf0256d6d2ec73b579d96e7aad6cf646f6f725bfc94ff4ff36ca0f2e7b
SocketDev~socket-patch~RNABDU.dockerbuild
18.1 KB
sha256:2283cf8a74645f8b18d0aaf99980cd92ecec0abdc14f2a90367bb5b1eafd718a
SocketDev~socket-patch~SBJ82A.dockerbuild
34.8 KB
sha256:ee9d45af716a67f7115e9d2a429d97269d202825b89addbcf4321cad0fd9f176
SocketDev~socket-patch~TAF36P.dockerbuild
33.8 KB
sha256:1405b23b1e2dc43a079e0efcf9ae09df59810ecf350714a78cfda902c0beb8f3
SocketDev~socket-patch~TTPRIJ.dockerbuild
20.4 KB
sha256:72a20dd311cd39d9db65262ae049d2130c7343f98e68ec470e4cd6add40bd473
SocketDev~socket-patch~U8T6DA.dockerbuild
19 KB
sha256:cbf5b71211a7bb96d21e07b6067f70e052e597e28798a88dd9f6e727e0b8c8a6
SocketDev~socket-patch~UN5XWL.dockerbuild
33.8 KB
sha256:5d95b45efa1242dba2e8b4e212720ee16e8c64e7172dd4f3b581aeacf3928cba
SocketDev~socket-patch~UR6SWR.dockerbuild
16 KB
sha256:5d716fcc05ebc532cca884cd03ee353e86f27b8d643070abd07782f7d665b173
SocketDev~socket-patch~V40WG0.dockerbuild
33.6 KB
sha256:f6fb17fdbd58bd5f2503196ba445a3c873fff61b095c556837783764ae70ec4f
SocketDev~socket-patch~VZXPUL.dockerbuild
32.7 KB
sha256:8d68d0c558f19e4e75f0093bb6b13e327c75b6f6622ac35a735cdf9103ec939e
SocketDev~socket-patch~X4LGEI.dockerbuild
33.7 KB
sha256:dca227b249cbe86642d2f377b64c2dc63c1db9a85eff54049aebc6243a18b850
SocketDev~socket-patch~X5XAHB.dockerbuild
21.6 KB
sha256:d808088dd959ea46b907e6bb96cdde20412d3f5674a9e85af37553f46169542e
SocketDev~socket-patch~XLFLVQ.dockerbuild
34.2 KB
sha256:07a72c231bca5182ae1900e7b78afb2b66c65e2a90688a8082b3a603df31acd7
coverage-docker-cargo
27.6 KB
sha256:62e51b9594e8af7ab8b5e46179e7e4df44b57dd65f3fd63567b917b312aaafea
coverage-docker-composer
27.6 KB
sha256:32a9b717d7e999c6832c38c88681d5bd54a4f92c766239d2b346b0bcafc5ca00
coverage-docker-gem
27.6 KB
sha256:2b97dd2d00f86683d301507ca5d721c648960b0561e675bf06618e5ed8fb2fe5
coverage-docker-golang
27.6 KB
sha256:edc2be5ccfe73f67f6df2fdb36e70d5fe5084da800b9284da398369c0fd9aac0
coverage-docker-npm
27.6 KB
sha256:be62b17a7b056464f91a1515f71be4ff4b73d8088d06e2bf5fb8552d7916e51c
coverage-docker-pypi
27.6 KB
sha256:6745b34b9d97cbfde3dc16c0b4e9da56dbe5153320b0c41cfe5a7773a47392c2
coverage-host
132 KB
sha256:5d8f33fc1073e6382563042351197f0d4f8c944fa12d9b3b195ab27dab6cc5db