Skip to content

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

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

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

Triggered via pull request May 23, 2026 03:27
Status Failure
Total duration 15m 14s
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/
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 (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 (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 (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 (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/
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
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~055SCM.dockerbuild
33.4 KB
sha256:27a830305dd33a10157a3bb5a9249daa0bf630d0794f536524fc87af69872aff
SocketDev~socket-patch~0DW5XU.dockerbuild
34.2 KB
sha256:190b8f425fdb6244ce30c159f9d40ea388c57de08016bab646fb5b08f43fcb0b
SocketDev~socket-patch~29G8DI.dockerbuild
18.6 KB
sha256:0b2798a3b6b4155884a03894ead7e1849b73d84bb7b2ff6dab52b9341d8ed86f
SocketDev~socket-patch~2CJHDZ.dockerbuild
33.6 KB
sha256:d6b7dbfd53a5f0c58adfa35bdddd1a9dc4bca2cd952a49fff46644403695b32d
SocketDev~socket-patch~30B6Y4.dockerbuild
32.8 KB
sha256:82d4abda64f55652f7b3e84b71a7a68d6fe84dd12f6c8df04cdbccd9aada9928
SocketDev~socket-patch~3K9GFD.dockerbuild
21.6 KB
sha256:5e34e3dcf00daea4f81fb1f77b5c9869f1b8e33e8cb05cf34049a369419dc643
SocketDev~socket-patch~3KBYC9.dockerbuild
34.3 KB
sha256:32ad5e0f34c3faf43d84e756e17dbb7b376e30212974107fb79d966c3793ecf8
SocketDev~socket-patch~6V54UV.dockerbuild
15.4 KB
sha256:31bc346b9310dc9bce5d8367b56d4e6e665dee2551ca809e526319571f1dbace
SocketDev~socket-patch~9SF1H2.dockerbuild
33.6 KB
sha256:2b35a308fa67e4cfb7f23e52d30409c85e9bcf3bfadbed9976c7f118f72a917a
SocketDev~socket-patch~C4A5JJ.dockerbuild
34 KB
sha256:67522d6469a88cc21a384e233b78f8a7222c8136178ecc7867c1450eaf064b61
SocketDev~socket-patch~D00SGP.dockerbuild
17.7 KB
sha256:2396e2d1b418c5660d4c44c2987715354c9aee0de85e72752f62bdcf48ce7806
SocketDev~socket-patch~GEWZRS.dockerbuild
11.8 KB
sha256:4b834b1cc209923c68b505f28fcd5540a5176ffe360e3abfb3cce8333bf807a4
SocketDev~socket-patch~I8G0OF.dockerbuild
20.9 KB
sha256:8c9267621acb8de719ef0d21f3a30ca6a25954c6db503b3b2555209dcae24687
SocketDev~socket-patch~J9E3RL.dockerbuild
33.6 KB
sha256:56aeeddfc1659c7c8d2e2243099bdf6a1dea54d388641ca6cc2800aa0470c1e6
SocketDev~socket-patch~JTEZYU.dockerbuild
34.1 KB
sha256:bd1684f68e7dc91d080e874b94910ede8ac5eecb6bc79a653d10acd997a53a89
SocketDev~socket-patch~M7IHQ5.dockerbuild
11.9 KB
sha256:73b764c2ec1abb4b291e78801dbcffccba1362f309d1ff2d29c88410f1b5fa09
SocketDev~socket-patch~MLSH2H.dockerbuild
33.1 KB
sha256:4d15ad5985dcb77758c8f876b1fe46385f14728feef00dc74916cea7650676e8
SocketDev~socket-patch~N24YFP.dockerbuild
33.5 KB
sha256:0aaa5356393a076882b779b8ebbfca2add367210bd5c559ce5969457d2d03405
SocketDev~socket-patch~P6L0RR.dockerbuild
24 KB
sha256:cab665bab345f52b145dad3a148d65677f9600533ca8855924e0e66a218594fe
SocketDev~socket-patch~QRWEA8.dockerbuild
35 KB
sha256:28ed66c18b92a38dd9f95f3a82cdf62105a3078a3d8a909005726de347de7908
SocketDev~socket-patch~RJ3Z4B.dockerbuild
20.1 KB
sha256:67fac7fbf6540cd9cd1384000ef720d0316ab241cb2167acc7ab28e2e0e6c2d4
SocketDev~socket-patch~RROJLA.dockerbuild
18.9 KB
sha256:90f1b53526cf7a7d31c2e6cf9127208cde8eccb11f5683125631438b71b9a1e8
SocketDev~socket-patch~VP90EJ.dockerbuild
33.5 KB
sha256:2a12d3ecc949670d1bc4bdae81a9db081de4f6fa33f1909c022dc0b661d983b4
SocketDev~socket-patch~WADHUE.dockerbuild
18.8 KB
sha256:faf2f7757544e2ad6ab0902488a09551f0e0e64983c439cd91e15cb930c8f17f
SocketDev~socket-patch~WC5T6V.dockerbuild
24.3 KB
sha256:b8d8ace53dad89fa1dd5e1869d54e04356c67164b6ba50bc7b1b42d1249912ba
SocketDev~socket-patch~WFZSO1.dockerbuild
33.4 KB
sha256:815ed1c39b73577d8d24a89e55c6f56369b024e15f6e43c1a54fd436911f388b
SocketDev~socket-patch~XYAND3.dockerbuild
18.5 KB
sha256:c26f330303de33e251fe0fcde392d8586bcd934a42df0873249427f0b071f33b
SocketDev~socket-patch~YERGQO.dockerbuild
15.6 KB
sha256:82b375c948eaa2a4d4bd96358b430fb1a6ffea07ca5e59fe4376efbb6fa6171c
SocketDev~socket-patch~YLVMHG.dockerbuild
17.1 KB
sha256:9b341703a7268d95e607d17f25afd8a530fb38abaaee932cf20376ce57ff0229
SocketDev~socket-patch~YYBKJH.dockerbuild
21.8 KB
sha256:f53dc2e95b241d7bd8a8b35dbae2fc0cfcfae8ec92d43894a11c7dac57c4a278
SocketDev~socket-patch~Z87F2Q.dockerbuild
33.5 KB
sha256:040f17177a23a651535d3f31c902679ba5544997247a1022423e725edbca09b2
SocketDev~socket-patch~ZN5SOM.dockerbuild
34 KB
sha256:3295b19a154f5f438577d22539e74242f0fae269e8cb5fdc5eb82c6b3c30cdc3
coverage-docker-cargo
27.6 KB
sha256:d4b0598fec4a4fe46dd830cbc39b8046e07417b372ab9293bd962715ec423ba2
coverage-docker-composer
27.6 KB
sha256:7d56f66fac734198e6bce1c35a94ab18657c8caffc82e4e1ba62e0a6fd068db1
coverage-docker-gem
27.6 KB
sha256:bcdae1417295a3265dcd0344c012f61f1e7916bed64e6437ebe34dc01c50e205
coverage-docker-golang
27.6 KB
sha256:2dae9d11ff2f7ae1efb93ce19052522b392b4fa059ba5b780d8eb80344c87c38
coverage-docker-npm
27.6 KB
sha256:568c1de6211b31aaa49a0ee4fc3ffe05465284d94222ba8f993e0802b1fb49a2
coverage-docker-pypi
27.6 KB
sha256:cf12cf4c1089338a9cdbd38de81986ba044b87e3458116208ec3ccdd0e7f18f0