Skip to content

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

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

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

Triggered via pull request May 23, 2026 11:45
Status Failure
Total duration 17m 11s
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

12 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 (windows-latest)
the remote end hung up unexpectedly
test (windows-latest)
could not read Username for 'https://github.com': terminal prompts disabled
test (windows-latest)
Cannot prompt because user interactivity has been disabled.
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 (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 (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 (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 (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~03O0B0.dockerbuild
17.5 KB
sha256:77a7a4bcd971a9934a831a3b72594670f46c3262620c7bdcd09f993abd7f2057
SocketDev~socket-patch~0JBWX7.dockerbuild
19.9 KB
sha256:060f2d9a266a0eeabbe08fc0a75d8c188cda345b38d02e9a2ff755748444d44d
SocketDev~socket-patch~8RSF2P.dockerbuild
33.6 KB
sha256:9602017310b944e249b9797d927bd94082d6634284ae2f4ba6550c6d3af75c84
SocketDev~socket-patch~8WUW7Z.dockerbuild
33.6 KB
sha256:93acb166f112cd79631a6eb08ee7179bfb8133018f36f68aaf8aab147198a2c5
SocketDev~socket-patch~8XH4N7.dockerbuild
32.7 KB
sha256:b31fdffc6fe79ab1d3e5fa690105c443f90d5ce6ee96fc1218c2cb60f59d8785
SocketDev~socket-patch~9Y10K4.dockerbuild
32.7 KB
sha256:f1632ca3212dd210f0c4ea91348c74ab7cb050affb3b95f407b018e9e6dc50a4
SocketDev~socket-patch~AQ9T7C.dockerbuild
18.4 KB
sha256:2ea0d8d8e9d8392b5b952990995dd59868ddb7f165370761a793cff9a9846e84
SocketDev~socket-patch~CMXB89.dockerbuild
32.8 KB
sha256:2b25061737ad5918213a93e5f5d1b59ec6f5d1e22dffc6e5d1a0b242a6bb3101
SocketDev~socket-patch~DK8T19.dockerbuild
33.9 KB
sha256:937d8f0a5f45e471253bc9c72fc7ea72af3c152a580750b3b33a3aee95cb9782
SocketDev~socket-patch~IJX7NH.dockerbuild
11.5 KB
sha256:8917ca68399f59c37f17b77d1f85cf8ee8509f92987212b1fbb0276329fd3910
SocketDev~socket-patch~IKVC3V.dockerbuild
18.3 KB
sha256:eec96580f64b33aaec3281ed3da7d6571b08553234d55aa19c6d60bb75c8cfde
SocketDev~socket-patch~L4T2AY.dockerbuild
23.6 KB
sha256:6e7510a27dffc6887a6fa1041af760277f1a4e33050c1f430cd32f3df55939be
SocketDev~socket-patch~LNK4SW.dockerbuild
16.8 KB
sha256:b1d4a07e7b887321247c14b3c1c50a328687b0ad146f70bcbe25db6966bdba45
SocketDev~socket-patch~LW6X1G.dockerbuild
33.1 KB
sha256:5afcf626c2cbb35db2554335116a980751beccd73b29d9b4421d93ae639991db
SocketDev~socket-patch~MJ3E2M.dockerbuild
21.7 KB
sha256:f8c541350dda812b9338561075fe2368d385c1cd90c72b0e5c746bf19d4b1608
SocketDev~socket-patch~MMRCX9.dockerbuild
21.7 KB
sha256:556862f83675bd9f16892a98724fccb9ec56e426df0802395437001b36e01f16
SocketDev~socket-patch~N0Z3IK.dockerbuild
17.6 KB
sha256:d8e2a1318a54aab015c01b7c472fa446f693f22c2c22051a2960d7fcedcb6df5
SocketDev~socket-patch~N5UST8.dockerbuild
33.6 KB
sha256:28a4098024b4b60046c4deedea4c72db8faae542fe52f39da23078b271df3ec4
SocketDev~socket-patch~NJAXKO.dockerbuild
18.2 KB
sha256:a6bc0662733e59843c67fd4e8fc7c953d090821124f8ccde2cd98662f6dbd56b
SocketDev~socket-patch~O6YI11.dockerbuild
11.7 KB
sha256:cf32be722c9b1e702685fdcd42dcb01c7580ecc60244cfa8186e9605323d3265
SocketDev~socket-patch~OYAF9K.dockerbuild
33.4 KB
sha256:b7378bfbf659b36667f496d7d578945548bdf39932003530c8de5a8570fb1da7
SocketDev~socket-patch~P725OG.dockerbuild
33.4 KB
sha256:df21be9634b5af42b14b51695b0cd18bf7d5070b9fc1c6b60a5279b623f1b3ac
SocketDev~socket-patch~Q4MFS5.dockerbuild
17.8 KB
sha256:80b6f58a1a941b3c7c586ee6d9885dd25e3ef6f23ec563b9ad92c346cce1f20a
SocketDev~socket-patch~Q92JCE.dockerbuild
20.3 KB
sha256:3c85d6343fb603520e2d33606d203689e00f050778da16ee0a4853e8dd994ea1
SocketDev~socket-patch~RLQW3W.dockerbuild
33.4 KB
sha256:958018f1bd7a14fcf8afbce2f8aaaa0dcf54d5f77e81cbc034b5fabf49354368
SocketDev~socket-patch~RYBA32.dockerbuild
33.5 KB
sha256:dc61adc69aa7ca4b8137a8de20d20a977d7e49fc7d060209f5d37ab479f226be
SocketDev~socket-patch~UOJ0SR.dockerbuild
17 KB
sha256:c5d494ee01addd86a1e9a5fdf9bf9e459c42b27cf7969ff59051279df2b38812
SocketDev~socket-patch~VGEKV7.dockerbuild
33.8 KB
sha256:f2a648d9f605f8636baa69767d758dbaf06b16eaa7d7c218a07c2fa548f0e905
SocketDev~socket-patch~WYYE79.dockerbuild
33.9 KB
sha256:41a2ddb84aae59f754367b8f02a4e12404924cc35e7be29e7ad85bd201764368
SocketDev~socket-patch~XRX0GS.dockerbuild
34.1 KB
sha256:782fbe231288840c7a18d04eb0988aeb2a529736ad5cdec63a5888e155a93c41
SocketDev~socket-patch~YX86GV.dockerbuild
33.4 KB
sha256:4cbdc87a6341b97dbcad7887fd61d7601d23d91cdec24b01bda8e6a712d749a5
SocketDev~socket-patch~Z4SXYR.dockerbuild
23.9 KB
sha256:ea473537a9c13c6fa5d8cd972ba46f4c153662c20f09c549efff49ba8937b374
coverage-docker-cargo Expired
28.1 KB
sha256:796f16a917d73f82f077fb0cd065f86672b25fcae2185084677ca15c1fb813b6
coverage-docker-composer Expired
28.1 KB
sha256:2279fc78f9bb1ef53764f160abf00f60fbc79501e259e5f959cad60d4dc12e74
coverage-docker-gem Expired
28.1 KB
sha256:b31e61271e113f6ac13bf00cbfca00930a09d636f381549b3d85356a7bc06db5
coverage-docker-golang Expired
28.1 KB
sha256:16b19428f9f536e4f6b0a4a3eadb3ee6864516069049268d8c341ec2c9d761d7
coverage-docker-npm Expired
28.1 KB
sha256:9bd3e73caa9ede50a09a91bfeae55719bb35c34bd781534d517b31d320053419
coverage-docker-pypi Expired
28.1 KB
sha256:de20d558797e1029725b254c9f46e21a9c2afcbe487e021e35e7e9f6d04085a8