Skip to content

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

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

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

Triggered via pull request May 23, 2026 00:39
Status Failure
Total duration 9m 10s
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.
coverage-docker (nuget)
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.
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/
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/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/
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 (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 (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 (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/
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~00YQY2.dockerbuild
34.8 KB
sha256:225530aae97c37a29c80b3bade10c228488d03d433cf03a33b27f351e4f6b584
SocketDev~socket-patch~04BQ1T.dockerbuild
18.5 KB
sha256:7c66104ec29e639ee6c75d90664517802a28ceff579eec5365182505949b7fc8
SocketDev~socket-patch~1GGWSI.dockerbuild
24 KB
sha256:c810fc9517e10952ab49251934506a55e6b6384b6e3c23eb3320fa271af402ac
SocketDev~socket-patch~2J4WVC.dockerbuild
32.9 KB
sha256:e6bd16dfd0290efed6a74b7a2a9b1abf8915a17e518bbc556c830bbd66ad7079
SocketDev~socket-patch~3B37XS.dockerbuild
20.1 KB
sha256:2c798981afe192546b59416dbc09b8c907e520c63a847b109af6089dee83fa6c
SocketDev~socket-patch~3GD9ZN.dockerbuild
16.2 KB
sha256:61d6e51fdc6170e8de2e9812faec0d45043baeda251f92cea79a3e6368069ea0
SocketDev~socket-patch~3SJ6QC.dockerbuild
22.3 KB
sha256:c17b79ee8b8b05e13a7b095da36b313f77592c5f80b7824f0a3b38af45d8577c
SocketDev~socket-patch~5CFQP3.dockerbuild
33.9 KB
sha256:2378c7041ccd0a04ddb18f2d999d7b1b5e9ccfe9e04991f229edab06d8de1a25
SocketDev~socket-patch~6ATBKR.dockerbuild
18.4 KB
sha256:a75715b43ba87f1b7ff3dc185a7c1e3e386e2dde20ae6307bab7a0ec8804fb94
SocketDev~socket-patch~7JV6PI.dockerbuild
12.1 KB
sha256:d57d154f322c815e1c2549c584a240e32953d6b38eaf27fc78cdebbcbf3c4a41
SocketDev~socket-patch~90HSKV.dockerbuild
33.4 KB
sha256:a9c66e2ac4a07484f74bca5759060df23db56ccbd6621fbd19569bd552f11321
SocketDev~socket-patch~A7DS50.dockerbuild
33.4 KB
sha256:aa14e454685cd711e838c3352fc7d9de8a092095730073a9d8dabe9aabb02c45
SocketDev~socket-patch~DINQ3B.dockerbuild
18 KB
sha256:5f76d532ca9be42544acd5b01ae39fbd97ad03e38213db35ef0202e510144bd7
SocketDev~socket-patch~I2ZKBV.dockerbuild
34.7 KB
sha256:a1caf35378dc6d8a19ac707d9187e47f59e1c663106df715cb503f4bd86b710a
SocketDev~socket-patch~IBTUSR.dockerbuild
33.8 KB
sha256:aef6344324c1c481b52cc02328c67b90f914074eac6f4aaac23294e26b234b65
SocketDev~socket-patch~JFI7I6.dockerbuild
24.6 KB
sha256:2ad305706457be3b1a9d8af6537e3e335d00998cfd722a734f012872e356f88b
SocketDev~socket-patch~JK9DGR.dockerbuild
18.4 KB
sha256:53e8eb6ce1989621a6cf5d6a67c9bbd7e20d88595467309a0e1450c5d744621f
SocketDev~socket-patch~K19JVF.dockerbuild
34.2 KB
sha256:b33e3c6142305b8561e46cd850b47ddc125396c49c3d570fe6fa72b3f96217c1
SocketDev~socket-patch~KLH336.dockerbuild
34.6 KB
sha256:f6e4f3bde29c7e5dfbe3b49dd8409c85bb524237c362ff0f99f6be6fc600f30a
SocketDev~socket-patch~LCWGIP.dockerbuild
16 KB
sha256:859d1f842ee6c80f8bb17f3316c9286c63d887f757d8b2591b7c56e407d76648
SocketDev~socket-patch~P24FXT.dockerbuild
11.8 KB
sha256:c2379138b05a87991bfdb1a040c7b3d7bab90b691aa9c273fc17603b7a5739c2
SocketDev~socket-patch~P902TB.dockerbuild
34 KB
sha256:70c76ead9e52649f3c8e1dea357898eeb2db7c931608a13fb027885fae10ceff
SocketDev~socket-patch~PXUGDB.dockerbuild
16.9 KB
sha256:9207115d16217dd3df1c6f469ec6b46f27544813ea07fe123f330831598a2fec
SocketDev~socket-patch~RB2FKB.dockerbuild
34 KB
sha256:cc8204546dc7b6d27f0352f9a401e411deebea0fb3fd7e0cd2481692488a3d9a
SocketDev~socket-patch~U8KIXF.dockerbuild
21.8 KB
sha256:9e30a729b4872a0e0692a925f3b9b7db11abb9bf2453a26a6445788b57dc376a
SocketDev~socket-patch~XSSW14.dockerbuild
19.5 KB
sha256:9be89fb45c67ec8774645a090f7aa2eb5e4794386c8c5302427f68146e2bea51
SocketDev~socket-patch~YGQEQ6.dockerbuild
33.1 KB
sha256:a74ce0cb1e534b662208a52d5332a54f7e361b15934cee1e6e0eac6888d5c984
SocketDev~socket-patch~YWO51G.dockerbuild
15.9 KB
sha256:8d49d4a2cec74ca523156afe5e6097ce625e7102654d86937593a4541b6af7ef
SocketDev~socket-patch~ZBMX51.dockerbuild
34.1 KB
sha256:42115776a7889afd71ca611399896ffaa653db0468b073c1380773dcd5fa302c
SocketDev~socket-patch~ZCSH6S.dockerbuild
33.6 KB
sha256:ab51678db9dd8a9fc1225326d5cc1746ad90f673c286d087f4ce4228ad625ddf
SocketDev~socket-patch~ZNZ3K3.dockerbuild
33.5 KB
sha256:7713d6dcecb01ef34d4d0d0b21bc0a0d1368276661d8909106b645686f7f869d
SocketDev~socket-patch~ZWUJ56.dockerbuild
34.1 KB
sha256:b7b7bd2e7c76741532ce7cfd5f353e04ce1820b71c101718762a37a69a6fa4d1
coverage-docker-cargo
27.6 KB
sha256:5454bb7f64880c6424a5e0a13ea99b87dbbda2574387105734ec9790962e23c6
coverage-docker-composer
27.6 KB
sha256:04aed27a11053fab597b70d0ffb729b619a63d721fe71c41ca478e11eca12daa
coverage-docker-gem
27.6 KB
sha256:d5e90b1233fc20cdd49b19e2c7ec8a663594ea6e6cec34d2c8a1098d4fd17b86
coverage-docker-golang
27.6 KB
sha256:9fac09f853c37dbc9c5d0ff2cd2fe99fcab37088dccb4fd5d794a86338c69ff9
coverage-docker-npm
27.6 KB
sha256:a7552274350b7aa6f8c5d8fc298ebe24dca53e9d5259dcc11f4bfedc3494ff3c
coverage-docker-pypi
27.6 KB
sha256:42090702bae9ba23585018518d10e24c7ef6c5d07c428c0eb2cbe80c99ae3b49
coverage-host
133 KB
sha256:51e79da200f419c4c0a3701da8d090f2259521f447b33d5660506f80f56fd69d