Skip to content

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

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

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

Triggered via pull request May 23, 2026 02:59
Status Failure
Total duration 12m 14s
Artifacts 38

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: e2e
coverage-merge
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 (maven)
Process completed with exit code 101.
coverage-docker (nuget)
Process completed with exit code 101.
coverage
Process completed with exit code 101.
test (ubuntu-latest)
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 (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 (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 (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 (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-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
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/
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~24H2VZ.dockerbuild
33.2 KB
sha256:c120f4fcc882a76bacd742ebccf0a79f0fe304554876065b222f134e523d577b
SocketDev~socket-patch~2XV868.dockerbuild
17.3 KB
sha256:b93c727f87ef4eafdb1922f6b9f85d60388d017d9d32489a778453d6e62aa233
SocketDev~socket-patch~7QFIKT.dockerbuild
34 KB
sha256:b35cf889c83bedc4450872726605846727b1d78f1fabf650d32bdc7a6e96b78b
SocketDev~socket-patch~8GX34A.dockerbuild
15.7 KB
sha256:423ef563dcf2e74422917da5526cdb1ecd428a562ae7e94f3f9a1002049db205
SocketDev~socket-patch~A8S070.dockerbuild
20.5 KB
sha256:923dbc23cda5544f7acf7cf983209ef8b64d3d22e90ec3d7e5dba5270bae3a9d
SocketDev~socket-patch~AS30JS.dockerbuild
22.1 KB
sha256:5bf6b524902b41ee64f82dd5939ce31c4b571086ac9c5c86f08a375f25c24015
SocketDev~socket-patch~B2N5XX.dockerbuild
18.3 KB
sha256:bd6ff3da5b6fb4124a4f4b57f3ec21a2d9fde88ce7beab7256d0edc4a5fef0f1
SocketDev~socket-patch~B90E5P.dockerbuild
24.3 KB
sha256:dadaf364a3a1ca608ed160527a7dca2d07d761175cdaacdd476a4ee50a4cec5f
SocketDev~socket-patch~E8L025.dockerbuild
23.4 KB
sha256:6e50cf1e681af1f53ffcd92c180d352e42a8799ffdb5e064ce4a95c237fa1c46
SocketDev~socket-patch~F5BAU6.dockerbuild
18.3 KB
sha256:a7581f424656d93ffc9931f8b4622048f74c2abf245475e80173372640651627
SocketDev~socket-patch~FF31HF.dockerbuild
16.7 KB
sha256:30752fce9eab79774ab3c54e96926a21bbbf4fd6fd916e9286ad3a8587fc6d31
SocketDev~socket-patch~K7PSKJ.dockerbuild
34.4 KB
sha256:cee25f670476b7dbf908fce6d4d44b06932c80d5287f16a16b2524e55441d2e1
SocketDev~socket-patch~KPKAV4.dockerbuild
34.4 KB
sha256:9a2301a071313c046cf5d51082bdf3650690ef0ffe13f1188fa62db85e68502f
SocketDev~socket-patch~LXIKKR.dockerbuild
22.3 KB
sha256:d55d811dfb9ace1f0476f2c0c4dd3458dd1c6bd33323690f09a1430fd4595992
SocketDev~socket-patch~MVQW3P.dockerbuild
33.3 KB
sha256:079a5c7308ea1a2f6f7f2cdd34707d40f8a57ef525913473e788f1c7d75a33db
SocketDev~socket-patch~NTO8T3.dockerbuild
32.8 KB
sha256:2528f18494ebc6cd6669f203f753ab5f2f5ad953d6c0884d9d6c3cc92ca914dd
SocketDev~socket-patch~P3H4OI.dockerbuild
19.3 KB
sha256:46e1674f2b1af8109c5937413c039ccb2a9d73639a4e3af793c7bd7370073fb1
SocketDev~socket-patch~Q9QUJY.dockerbuild
18.6 KB
sha256:8388667743a6c79488e20284ee25f7c51b7c968ee0b951cd54cf51fe1e9144cd
SocketDev~socket-patch~QRLLX5.dockerbuild
33.7 KB
sha256:2e15dde8b6ddee3e77200ddbef3e940366835cca21872938dc2b55a469eb5229
SocketDev~socket-patch~QS1T22.dockerbuild
33.9 KB
sha256:26c9ded693b685614cfa43cfda1179e31f281c995e1dd4e19029069656b16538
SocketDev~socket-patch~RKXLH3.dockerbuild
15.4 KB
sha256:d63231749957547c5ad451915d7c7b3b7d433ae6ae834980e99accef08ae1776
SocketDev~socket-patch~SDTYOV.dockerbuild
12 KB
sha256:2a07d14bd72d981c98bba9a541f850c71e5f743b0eede0356b8f831a9e617c14
SocketDev~socket-patch~SF5AIX.dockerbuild
33.8 KB
sha256:60840fbe9427961502e04973ac0b3ea0ffb8d91d51087220e6da600f1c364842
SocketDev~socket-patch~TH4891.dockerbuild
33.8 KB
sha256:cc6ec9196c0c54485bc5742148c7916472e4c57d6a2308b85b152f2b25849e19
SocketDev~socket-patch~TQLDB2.dockerbuild
19.9 KB
sha256:b6fa956621ef6d41fedf31ded0c2afb67417ee9d9d45ec9c195d0aad1b0d4478
SocketDev~socket-patch~ULLV9R.dockerbuild
34.3 KB
sha256:21af58aaf052583ef416cf454a4de4b554514b35f2624c948ea3d7245c779b85
SocketDev~socket-patch~W85LHI.dockerbuild
34.5 KB
sha256:604748b589b3d997230a42473403f0712abfc4f0897c7fe1574e25b8d8e88e6c
SocketDev~socket-patch~WU8QWE.dockerbuild
34.1 KB
sha256:76f5a0329205e6f8493554e8aa35792a1541a8c9b9fc7b49c570906b57b017b0
SocketDev~socket-patch~XC9J6A.dockerbuild
33.7 KB
sha256:2b9ef092f4926ff3d6c92eb7a7d8fe9254a1eb7eb6e5f07be4afd2b4498d7c56
SocketDev~socket-patch~XHE77N.dockerbuild
33.5 KB
sha256:024e32c3dbe6b69d3bb6e41122283877b881e165e1750956208c2eb0360fcdc5
SocketDev~socket-patch~Y0CXAG.dockerbuild
11.9 KB
sha256:9683885b1a64993f690847d68bdabc4e31de3990f34ea4757bfae98cb8fc68c0
SocketDev~socket-patch~YLLQAQ.dockerbuild
33.5 KB
sha256:dde65a811e0216f0ba24d148f5a1802c1b0c5429abbba352dd8aa18dca6c95ba
coverage-docker-cargo
27.6 KB
sha256:e8be4fdc0d0ae0047990735bd56736f42736fd8acde8b13d48d8822616901cd8
coverage-docker-composer
27.6 KB
sha256:b6590e47b9e5ae4b01e3def715f9b507d9c2eb02eb2f14e8d3a17eb24d946888
coverage-docker-gem
27.6 KB
sha256:be893c9630b2211a6ac052fb5c0a7f9f0d18585fd7b2f350903cc5daf8f5ef07
coverage-docker-golang
27.6 KB
sha256:76fc1dcecf2d62454640ea6099ffae39ff0243f595d602a76432268a808079cd
coverage-docker-npm
27.6 KB
sha256:c5a88404c3034c6b68a3f63ba48fc8352c0fe51953df28cf4ecc9b19b2147483
coverage-docker-pypi
27.6 KB
sha256:bf6a85f119684962d8874afbde27216fb5390253bc5b3fd64045ec4a9ee84d5e