Skip to content

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

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

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

Triggered via pull request May 23, 2026 02:24
Status Failure
Total duration 14m 0s
Artifacts 39

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

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 (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.
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 (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 (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 (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/
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/
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/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/
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~1BLT29.dockerbuild
17.4 KB
sha256:1d32b6a78468d7d7ff279f0c1f1a9aa3e14c129b8af5edb95926dedb235394ea
SocketDev~socket-patch~1P1CV0.dockerbuild
34 KB
sha256:4e86fab3f491b5d6d1151fd975a1e5944f23cb62ba0b4928c3d76ce9f95321be
SocketDev~socket-patch~74Q1G6.dockerbuild
18.4 KB
sha256:3f4041ea16bc21f21a1ee4f31cc56bdffb3c56a36349487eb5d2a3a966525c9a
SocketDev~socket-patch~BMJ7RN.dockerbuild
11.2 KB
sha256:86612b17650c42af803bf80ace3eb6b82714f05752f6806f254b28d1b19c3225
SocketDev~socket-patch~DMFDIC.dockerbuild
33.8 KB
sha256:a7ef6c55efad3513c62f1ea4bcf8350e96f199ff8fe0c087147e9bee427250e5
SocketDev~socket-patch~FMVNKH.dockerbuild
33.6 KB
sha256:c29ba1f18647a65b0a168fec2eb3dfcc8a747ab9f67827830fd5431946ea7e4c
SocketDev~socket-patch~G2B7B3.dockerbuild
33.4 KB
sha256:289d466a910f1a845ca8ae58feb64da5bfe3cf4774bf907ce9acfd1cff19d70e
SocketDev~socket-patch~GIXQG7.dockerbuild
23.5 KB
sha256:a1b711d37fcdb7cda69bf95c712e4f4d7d6c3de7e27ee723c805ac88a6f877f0
SocketDev~socket-patch~H3EUI7.dockerbuild
34.7 KB
sha256:a55de16b9b55bfbd8363ee11e4098ec624517fe2c4fb8921174264bb31e4bc2c
SocketDev~socket-patch~HX8HQ6.dockerbuild
33.3 KB
sha256:8576c9c8f225c61c289ac6b47365f05190d8dd397e05ff89333ecff3859f3c51
SocketDev~socket-patch~IKBCB1.dockerbuild
34.3 KB
sha256:a6b6713f6a8e26960a83cf53ecd98434b713d1f2676bdfc0a8dae50b9a683d30
SocketDev~socket-patch~IY3VFT.dockerbuild
24 KB
sha256:9463edd55198d6158ebfdafd77ca55916b689913ab99652f1470ae5863ea47a2
SocketDev~socket-patch~K7S7MF.dockerbuild
33.6 KB
sha256:f6e7add7e3c6d4e921049105e49c73946edcb5357b797a7dd93f849bbf1fb346
SocketDev~socket-patch~K7YDQY.dockerbuild
34.3 KB
sha256:77009094ce2c5be747fb8d183f1a82e3db6e53de0f066194ed5fc3ac8948b335
SocketDev~socket-patch~LQMLOX.dockerbuild
21.7 KB
sha256:5739123505e5bd7d08ca05c77db7c6c4c81d97b621560e345d54f95a9c38410d
SocketDev~socket-patch~NV3UAZ.dockerbuild
20.5 KB
sha256:f6eea937ad24052c54f119325781aadaba1da0113ea44b55e92601d513fde7fa
SocketDev~socket-patch~O0EGBC.dockerbuild
15.6 KB
sha256:f416cf0ff3176cbfad8d23f9bf4a17ab1aeedbdb3e77af63e13945b867843dc0
SocketDev~socket-patch~OIGGHI.dockerbuild
34 KB
sha256:42f94969677a620e815c1a458c75c18faab2fba046766b987f598961db0b2bba
SocketDev~socket-patch~ORXSLX.dockerbuild
33.1 KB
sha256:3262e5fca66e153276b1e589c65a0ef729d4dd981c040e8014d16afb642be55d
SocketDev~socket-patch~P166YT.dockerbuild
21.5 KB
sha256:897edbc0122ac87f0a4c75c913705ae6ea93925f6add62c831a28a2cc539d316
SocketDev~socket-patch~P372ME.dockerbuild
19.9 KB
sha256:b61ee08b6bd44c52ecbc2ddb5163b82dc15eca38467f778fedf238661702b021
SocketDev~socket-patch~RM19HE.dockerbuild
34.3 KB
sha256:905fde85ba70c2d63962556338793f826c0eeb6649893d1cbe5ed2ee28c045e6
SocketDev~socket-patch~T0TEXB.dockerbuild
33.6 KB
sha256:804d82af6e0b45c7760e0d9d7a869743164076b08a5be97170ffd4ecc62f48c6
SocketDev~socket-patch~VUS4RK.dockerbuild
16.2 KB
sha256:ce0a1cec98bba1f6617287d87d0399d44e12c2df4704f4cb3dc1ef851377fb10
SocketDev~socket-patch~WD4ZCY.dockerbuild
34.2 KB
sha256:d8f6fab909792ff56af8b1ef571c5ba7cb244dd8993fd350ff93e2b6eab2215d
SocketDev~socket-patch~WZY4LW.dockerbuild
33.6 KB
sha256:1905ded07b473069f9bc7aeb626fe8c16d0348971c3798194cc325dd53e24b1d
SocketDev~socket-patch~X16696.dockerbuild
18.7 KB
sha256:b7c439187729df64acab1da60aa75e193569acbbd5c6b7fa28783da79cad6963
SocketDev~socket-patch~X1VZEQ.dockerbuild
18.3 KB
sha256:5edbd7154663f5f3bace1998b9a434b1bb327c35d80be53978fceea27b546104
SocketDev~socket-patch~XIAJ2K.dockerbuild
33.6 KB
sha256:f713177b278e5737c4a3514f06e0f0dd18002a471bcae1cdbb1270be5a9f5c4e
SocketDev~socket-patch~XUZYSL.dockerbuild
11.5 KB
sha256:cbb871a887c8639bc4d0b268092bd72fa2591b4dd7dc662160a81bce449fc8f2
SocketDev~socket-patch~YFRON0.dockerbuild
18.1 KB
sha256:506b9027d6be8553edd2f67939f935468a076b8af5a0499d5c7df8e784567739
SocketDev~socket-patch~Z0ZKGK.dockerbuild
17.7 KB
sha256:3e15684f88dded6d63293bb7c66669de1e240d958e93b79889afcf761bddc750
coverage-docker-cargo
27.6 KB
sha256:9aa8c3ee6e865797e0fc188ae50e3a468598feaaa59394f2e001a5b8f19bec8e
coverage-docker-composer
27.6 KB
sha256:ea99287baf68f22208fe98ba55d5c0ebac2a8f18d86166ad7beace916d783d57
coverage-docker-gem
27.6 KB
sha256:0e639f647c82668e039b4e21becd6d9f4b647fad7ed78ef91b9cd75ecf73e1cd
coverage-docker-golang
27.6 KB
sha256:0b7f1220a334dfe523c31cc67fdd530b3b96a677fd18c12f2662b6c1b26c9b61
coverage-docker-npm
27.6 KB
sha256:315241f43eace019fe18f0c3cd2c6ca004e3b9eaf5a52e6be0e7669d5ba3048d
coverage-docker-pypi
27.6 KB
sha256:bfb718ad49004610f39982b7620d968fc65725ac8d874e84221bc56174197722
coverage-host
134 KB
sha256:a79361c6c4422808b010685dd87a3843b68611f2657767c5d100511a8e3ba85a