Skip to content

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

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

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

Triggered via pull request May 23, 2026 04:12
Status Failure
Total duration 17m 10s
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 (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 (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 (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~1SGQO6.dockerbuild
34 KB
sha256:00de3270d3c0d5512beafbc47a9eb265ceeebb30f14fbba42d4d32c068882ed6
SocketDev~socket-patch~5AA5F6.dockerbuild
34.1 KB
sha256:b5d1101dc9fbceeba9b0757ef1823115d34d902282eb4edf2ae5b5d2e503fa57
SocketDev~socket-patch~7CS1K1.dockerbuild
34.2 KB
sha256:e7199b59527848784447cc96319c4c894b99ac1b58fbdecd4018ebf79eb27153
SocketDev~socket-patch~7I7LF6.dockerbuild
33.2 KB
sha256:5985a6196538cd3ceec651fda9cd5fdb23b60b0dfc6ff571a9fc459f195bd75f
SocketDev~socket-patch~9YXLI8.dockerbuild
34.5 KB
sha256:7792981f7362c3eb2ab823335e4569afc6dcef2d95cbc3274bfe4eebbc577fe2
SocketDev~socket-patch~BS3BEY.dockerbuild
33 KB
sha256:32854d96c3081b6f32b6d1ed5223f88b69722eded6dfc92eb599f67ee0e166b5
SocketDev~socket-patch~HZO8OQ.dockerbuild
18.5 KB
sha256:6a16964edb590aa6275fe546834037a603fcd4fd2bb77a1174c8fe8217acaa0b
SocketDev~socket-patch~JPNLZN.dockerbuild
15.9 KB
sha256:8a953f9e7578c032db5a3aa01ac2087e4a91d5a1152dd271ec8c46e71494d71f
SocketDev~socket-patch~KWGXU7.dockerbuild
33.2 KB
sha256:3d2a9c87c8414120e7faa674e6cbcda2ce0cead4c50efc6dd5748d49199528f9
SocketDev~socket-patch~L2J8RV.dockerbuild
33.5 KB
sha256:00fd4818737a39893eed2fe48af0f295ef5f8b776d6cd7be10cc767e00c99ac6
SocketDev~socket-patch~L3ZVG5.dockerbuild
11.1 KB
sha256:5d4de08bc806d1a1eb8558b5e8efb289ba9df665c7494b10e7fb6915b3a70d6f
SocketDev~socket-patch~L9OU07.dockerbuild
11.6 KB
sha256:59b35c5ea0cfed121232413fba38d3b36412d8e7d1a310947f556b558cb78ffb
SocketDev~socket-patch~M161W1.dockerbuild
20.5 KB
sha256:bd473d5a85415282e02582fd429dea561e579fb277250333b0fbd944580844cd
SocketDev~socket-patch~N48LB1.dockerbuild
16.1 KB
sha256:59275261f58e638fbed6722a12adda06957931b84f1cee86f80dff3d8fecf192
SocketDev~socket-patch~P3WBI9.dockerbuild
34 KB
sha256:52f580bad6b10fe09c1aaa36e38f59891352957ceebed0980de769add495cecf
SocketDev~socket-patch~PSNBOH.dockerbuild
34.5 KB
sha256:5ce09ec85640266b1230729fd6c0776a998413022b306253c16b9238659d6260
SocketDev~socket-patch~PUQC0H.dockerbuild
33.6 KB
sha256:5f004c436be327baad819c985ede391590de977503891a24dc74002c1604e135
SocketDev~socket-patch~R4WAXI.dockerbuild
33.2 KB
sha256:b930426033eaa644e31b7875b4524b8de2cec3a9508c998f4c83aaca176bbffa
SocketDev~socket-patch~RDO6TT.dockerbuild
24 KB
sha256:28c2d78b21ae435a6faa475a8938fd78f2750760eb7de118506bf3cea9be6cf5
SocketDev~socket-patch~RRD6UN.dockerbuild
18.1 KB
sha256:93d6828c44e7adf5e2b1c3ab5225411fc3d8bc1bba46ef7712424e153d58f598
SocketDev~socket-patch~SEVK8Y.dockerbuild
19 KB
sha256:c71e8e01a7f2729472d0aa0a0809bc8e03e26e05d7a5d1ebdf23c208c782b508
SocketDev~socket-patch~T9BBJI.dockerbuild
21.1 KB
sha256:254d6d4404cb888d7bbe92e1b9b171eb3b24db5826f1ed8989c361daba3866d5
SocketDev~socket-patch~TEW1KI.dockerbuild
23.4 KB
sha256:a50c4215f09897da2b042ee989997685b7857b2a91ffa46bb5762ab0d8fe43c1
SocketDev~socket-patch~W6N6KJ.dockerbuild
21.6 KB
sha256:a3d32f1cfe896c0ace521af045cdf7eaed94b3a7f89aaa19cdfcc5e78a3dce54
SocketDev~socket-patch~WLYB8G.dockerbuild
33.8 KB
sha256:3db07adb32265bd5f6bc89c565fd78096400af30bfc7af771804f14ef9c78e96
SocketDev~socket-patch~XS8IVQ.dockerbuild
33.3 KB
sha256:aaf178280a95816a100357e0f4fb5a3cbc02a5891b3b10eba262e058282ac317
SocketDev~socket-patch~XVORGJ.dockerbuild
32.9 KB
sha256:339e7d3995e84c9d48faf3e45040081ceb98f63bfca5f3c9e52f073f7bbfd7ce
SocketDev~socket-patch~XYR1BT.dockerbuild
20.8 KB
sha256:73ba0f5752d5c190b01ae1c3146f3dff31ba0e0e24b82ef8d429842510caf097
SocketDev~socket-patch~Y6GKR1.dockerbuild
16.8 KB
sha256:ee3d22f19ef84542bd03acfd99625f2785801ced1ef057103e39f53861ab6109
SocketDev~socket-patch~Y7PZNC.dockerbuild
33.9 KB
sha256:b569ad09bf4323c7b1f37993da8fe4043fd3a512e68c624d582d8a136d655238
SocketDev~socket-patch~YLME9O.dockerbuild
18.6 KB
sha256:eae03a7b5dbbcfc9f540eade68340b5eb9f160c1657f59c8bda5678c4e69f573
SocketDev~socket-patch~ZCMBKC.dockerbuild
15.1 KB
sha256:8e888caf5163283395cd221d64b06ed7b979f1f60df85aa084c7e77f5cfeab94
coverage-docker-cargo
27.6 KB
sha256:f22499b10853d87d41a8c67b6d9e4eef4e9e04996bf054dd7a5424885c267f64
coverage-docker-composer
27.6 KB
sha256:7de424d2a692cbcd7931769761de62660f47e2c3b0f20e05d3e81d2ee2ce153f
coverage-docker-gem
27.6 KB
sha256:97fa0eb0c3b777fba46067f96d16ce0a06dc5b21c40e99284151acf2f68f7da3
coverage-docker-golang
27.6 KB
sha256:5e8ee497ddf1210ff9e773a230290ab0b11d00c35c647b8b4ff6c9b8cbc8c47e
coverage-docker-npm
27.6 KB
sha256:2acf788aa29b7a0bfa98ee7bf0d12e47a44ca69b734aabf5dd9d69bd0a230121
coverage-docker-pypi
27.6 KB
sha256:3538023612d8b6c44da6b9bbeaf9a4e8875fb34a548b983fbd156c4662c14a59