Skip to content

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

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

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

Triggered via pull request May 23, 2026 11:05
Status Failure
Total duration 18m 2s
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 (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 (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 (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/
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~0L2G35.dockerbuild
18.1 KB
sha256:74adffdafc16d5edc287e15a63ae6be15db08af50b3b2b318bb2ae7849b02532
SocketDev~socket-patch~178EPI.dockerbuild
33.5 KB
sha256:c17f7ba26abd32b4d3a55f8e2997e8210eb41e96e8280f5181373cd674c49db8
SocketDev~socket-patch~1JV4XK.dockerbuild
10.9 KB
sha256:0e4e4217b78d895e78ccca3fab69307dfd26a8844712aa67da20a092b09ee822
SocketDev~socket-patch~36S891.dockerbuild
33.4 KB
sha256:b8005c64f90bb80f12dd775215fd9923d18e663ec785c9811cafccf3dc7eca8b
SocketDev~socket-patch~8R3XS9.dockerbuild
18.4 KB
sha256:29ff65918cebeba37fadc2047d8455e661a862b18793125c2a36d1c8c346a459
SocketDev~socket-patch~8WZ50A.dockerbuild
16.8 KB
sha256:168d94f8cf6b538c930afde1612471845900d740caef0715bee28010cdc2088d
SocketDev~socket-patch~A7CKKH.dockerbuild
15 KB
sha256:546fa66caffcec2527a6fc8a0c2a6f17d120cc826aa9f5734042d2d8db0e94cd
SocketDev~socket-patch~AXLQQH.dockerbuild
34 KB
sha256:9667d170dd852b1821b1e62499bad07e62fb2dd1b9cbb968f14ccd89b72061b4
SocketDev~socket-patch~B0TXQA.dockerbuild
33.4 KB
sha256:591fa2745502e914d5792e56c378e961b9f3ed63d9155b59e5bab2af0f918fac
SocketDev~socket-patch~CHLJ35.dockerbuild
33.8 KB
sha256:fd39e2f4481419c01ab7173968784c82d127be87a445288f701a276be2a7c2aa
SocketDev~socket-patch~DFSOB2.dockerbuild
33.8 KB
sha256:9255acf4103e163bad9d04713761bce6c67cbd0eca3e893dab3d9a30dc8e1776
SocketDev~socket-patch~DUZBF2.dockerbuild
33.5 KB
sha256:2a7c5795a727864bfb4543315ad3c737ef7dbc88c6913b57e744933ce414ae1a
SocketDev~socket-patch~G3MQ8L.dockerbuild
33.6 KB
sha256:635fba04e66b2413e9cf98e1ae23a7a004d5d4c90aa57c29586ee9006264d6cc
SocketDev~socket-patch~IBM7XK.dockerbuild
33.9 KB
sha256:b49fcb7b77e4914b0cf1472a0f6b4576a0abb7002c2eccb969c7b965b3dec858
SocketDev~socket-patch~IPO1FN.dockerbuild
32.6 KB
sha256:af1149a724112bfe50c8d47cf549f45be09c297187de5de64d9311e1609eccb8
SocketDev~socket-patch~IS10GD.dockerbuild
21 KB
sha256:fc4868818de1ea765debff88d9fecdd0fbfbf3c7a94db77025d520c6670ac28a
SocketDev~socket-patch~IWLRWP.dockerbuild
18.3 KB
sha256:0b180418f5352641eec0536a287c883de604b9bb7900cb674f15836c5af10305
SocketDev~socket-patch~K9K7GU.dockerbuild
34.3 KB
sha256:cd5f0b1a397a4e6b0e4f2ab201d364cf8236ce0c375730e3f2f8885d66709a0a
SocketDev~socket-patch~LOYZVA.dockerbuild
23.4 KB
sha256:c234b59a9cee3ebc29840323f3227c9e1e1328fea8084f88d912922464b56bf4
SocketDev~socket-patch~M7HTE6.dockerbuild
16.5 KB
sha256:4f4681c3da4ad7106804b5d3acd98c018ea9fc16d2cfca6fad4422e15b317681
SocketDev~socket-patch~ML63BV.dockerbuild
21.6 KB
sha256:fad99dcec1a7866cff6862dcf5dd611110dae5cda6dbcdc86cbb76a83f779f15
SocketDev~socket-patch~QFZXK9.dockerbuild
11.1 KB
sha256:71a4b1faf90d45fa8db21982794d0de4d93c61310d711a7964dd2007b3e0f345
SocketDev~socket-patch~R43574.dockerbuild
33.2 KB
sha256:1beb653cc93b26598e2c184e3f420668fa4191d23e4a9c228eeec864551784e5
SocketDev~socket-patch~R5NED3.dockerbuild
34 KB
sha256:4e90bf22e86f669e6838c84a2fedbe1fd14fddeda556a4a937cd8db4a920c7a6
SocketDev~socket-patch~SFDWMW.dockerbuild
34.1 KB
sha256:7a8adf09b647bd973a45d0b28b69c45d3cf56f5ce355b225dc5b78666a213954
SocketDev~socket-patch~SGI0NJ.dockerbuild
15.7 KB
sha256:f668a5f0a7c1450a017a74e70f66a96e61fb25daa12a559b805585037e50889a
SocketDev~socket-patch~SL23HR.dockerbuild
18.3 KB
sha256:f81d8e433c52665721d876594cb4209045e089ecd3c0d768059a1692a8ab47b1
SocketDev~socket-patch~VLBPIJ.dockerbuild
33.6 KB
sha256:e665cf2dd6ad5dcdc45310d7d3cb9c833676734430d767ec0cbea2cd9f17cadf
SocketDev~socket-patch~W8C002.dockerbuild
33.2 KB
sha256:71bc933103a570bddc28401a7b55dd810d5168c60cdb54fd772bb4b55a2c21a1
SocketDev~socket-patch~WD1HWD.dockerbuild
20 KB
sha256:712089253138c9295eaa15a7fba0492411e4ca220532b84a96b38ea9f6eb8855
SocketDev~socket-patch~X2U7JN.dockerbuild
20.8 KB
sha256:708e73e7dae26ab5d1b6cc654e33283c8e3b21c8eb9702999e6ca8cc086f199f
SocketDev~socket-patch~XIG8XJ.dockerbuild
24 KB
sha256:cb8a61fa0fd7a7b1ab6d8e0a50054623a75fe316780e2a246ed8640ff0a840c5
coverage-docker-cargo
28 KB
sha256:c6deb8282c28d908ecbfc23b09a590438d848c85ba33f1b94c506588c0d9e914
coverage-docker-composer
28 KB
sha256:0fe07e5edfcd03efe27c407263c4e0f465080383f47d93b6189f4243df60942a
coverage-docker-gem
28 KB
sha256:94db42da01c31fa343969a030a70b8bfe89c501bb6f479b2ede74dbce0ed9d39
coverage-docker-golang
28 KB
sha256:baac4c7298dcdd722df59219a5f1978c0aa1a5f80ca0e100997ef75e55f8761a
coverage-docker-npm
28 KB
sha256:625713b3331c0e9e2e93ac49310a584797d36ee123c0e40fca6c11072a618cdb
coverage-docker-pypi
28 KB
sha256:83a6449c1001d12717ff0a22264aac0b529634f604c56c85b6a7b8293d28c1a5