Skip to content

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

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

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

Triggered via pull request May 23, 2026 03:08
Status Failure
Total duration 11m 37s
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.
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 (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 (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
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/
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~0KNHKW.dockerbuild
17.1 KB
sha256:9b4c7f187ac52d16af7eb36d814d35ee950189cdcf2da59437efcfffc97637d0
SocketDev~socket-patch~0TUWTJ.dockerbuild
33.8 KB
sha256:5eeb998d7a51855d03e955ee4f986882b9497799b7b8bfe297292e4575be3f26
SocketDev~socket-patch~1KUNJO.dockerbuild
34.4 KB
sha256:f31161b3223977e852787dab47f78506c75e4e4b6524b0b7a5195326f400472b
SocketDev~socket-patch~1TYZ80.dockerbuild
33.3 KB
sha256:c55c796a37894b1667a7ebd5a63dae4c5c1f72b75457b98120aa426b1e0aaa07
SocketDev~socket-patch~3X45OQ.dockerbuild
11.1 KB
sha256:d775b8d21377a1f40bb4da149a500d7ad8f0340719841b4a03a6198791757446
SocketDev~socket-patch~5PGNLY.dockerbuild
23.6 KB
sha256:bef3675d4d5237c492ad829fb6e313752fd52950ed5bf39a03c98ce3acde0d9f
SocketDev~socket-patch~6EZQ2L.dockerbuild
22.1 KB
sha256:5f215588194577fe15a325e70b9e49c7023943df2857268cf9363e5936bb51c1
SocketDev~socket-patch~8S2LK9.dockerbuild
34 KB
sha256:31d18bb0fb227bd791751e2548f8ceae214417965b959e03e97edaf7fb3bfa52
SocketDev~socket-patch~9QEGC5.dockerbuild
34 KB
sha256:979ba5b51dcf4de0b36b67aa122d353ecae8870c635a36a9e58c8cf0ee6cbc56
SocketDev~socket-patch~9V56I9.dockerbuild
33.9 KB
sha256:598f75de76acecd152c0bff82a3a9d8b7819b50104df8beb7cca4e4c248cb206
SocketDev~socket-patch~9YAIC5.dockerbuild
21.5 KB
sha256:8f3207fc6cccab79cd8def0deb067101794f1c9b153b5071f655587189998e43
SocketDev~socket-patch~D4LRNZ.dockerbuild
34.3 KB
sha256:9023b8568cc4c08b8e8c23c34f6d6adee1c74248cddfb7fa94b4c02e540c6899
SocketDev~socket-patch~HFD7T3.dockerbuild
33.7 KB
sha256:83fa24b0b3ca8d9390d9e3740074124e104d8655887be4694a84bcd586839d78
SocketDev~socket-patch~HXZ5FM.dockerbuild
16.9 KB
sha256:dd7db00aa6a9daea33c47ea761a44aa794a1d6ea541677a42e25b454a000b4d9
SocketDev~socket-patch~JLZTI9.dockerbuild
33.6 KB
sha256:80a08c57aadcd4166c257857e63445bea37ce5136c1d5431f61538f5e7ef6497
SocketDev~socket-patch~JWP96K.dockerbuild
15.4 KB
sha256:a0f04b554503acae6307be7dbe30c04c0db52d21bcaaf96853536dd1a3181661
SocketDev~socket-patch~KPGHRV.dockerbuild
32.9 KB
sha256:49e5ae8530a554be8e9ea47cb12869ee02f899865136d4ce441e4fc54ab5803b
SocketDev~socket-patch~LJV3AT.dockerbuild
23.9 KB
sha256:a3b29d70cc89bb5d02fed67dfb6177374605d9b038908d04c29b4eb3c788cf82
SocketDev~socket-patch~N28OWC.dockerbuild
18.6 KB
sha256:cb002b85da3d90500c99085cceb3f8b77b42ab52fe0a5da271c5adcbc088d4ca
SocketDev~socket-patch~NH4IRG.dockerbuild
11 KB
sha256:5bb5a22509cfd31895572b088971ef353a4448742a981edc37ee20ed4484f933
SocketDev~socket-patch~NKUQNB.dockerbuild
33.2 KB
sha256:d180f1af160af3afa1902d5459ef053fe19c898ec9c6c3559d45106e4d6923e4
SocketDev~socket-patch~NTE8RB.dockerbuild
20.6 KB
sha256:fb1c41b518548b0332782793d613c49b2bb6f0fb103d640449e3bb9d2a676196
SocketDev~socket-patch~PBJU9K.dockerbuild
33.5 KB
sha256:6913fb1267944195f320df7d345e6503b4ef70501bf38696a0ad730edc87806d
SocketDev~socket-patch~PIMVM4.dockerbuild
18.4 KB
sha256:1749f046834d5aa318fe14cbe3f032fd06246d39c24540b3203f1bfbe9dc1c0b
SocketDev~socket-patch~R5CV10.dockerbuild
33 KB
sha256:eb316eb86fe129aff453db462dfa3a0ae0fb4afb59f93e2ae0229fee6122be3a
SocketDev~socket-patch~RL0TJ6.dockerbuild
19.8 KB
sha256:a816b8229556e6acba4488bc7eb92db04759a3784fd0247b572c17a76e32946f
SocketDev~socket-patch~S3LL89.dockerbuild
32.8 KB
sha256:3def1bd6205bf6b2d3dc7e4596af6f40ab0070598ba6f3fff51be3ce9b9312a2
SocketDev~socket-patch~SO13RK.dockerbuild
17.6 KB
sha256:984aeed2c8c475f9045bd2172765de368ee5919e1202e90926943391969e74cf
SocketDev~socket-patch~SUKAF0.dockerbuild
15.7 KB
sha256:06a7bd2ee44ba42e771ce398aa6ed204a425d5d1cef9b0440095ea5d5567ce22
SocketDev~socket-patch~TDXTK3.dockerbuild
33.6 KB
sha256:12ff59ea16cf4abf2868dde0dc3d710e371fe3cd428da3cd8aa65e0736fb4ff1
SocketDev~socket-patch~W59UWP.dockerbuild
33.1 KB
sha256:232642a762c017141ffff72a5dc27da6f1767cacb53702888e69f6c32b4f8a28
SocketDev~socket-patch~YHVOSF.dockerbuild
17.4 KB
sha256:784d35ec4984c37a0058b2fb9631543a8dff61b33493a931b222159a64450b51
coverage-docker-cargo
27.6 KB
sha256:5948f4d71edf4ee27511edc3343c8607a84e647a7575c956002d16fee1389adb
coverage-docker-composer
27.6 KB
sha256:391e50adaa1dc33ca415d0726cb6968c02897055f867bc2d2e40b89ac487c103
coverage-docker-gem
27.6 KB
sha256:5b4a2857b5ac03da8131609d3234839f8b083dfdd5cd7a0967f25bea6250acf2
coverage-docker-golang
27.6 KB
sha256:19007f998385866c60101e31ba71c890104d0438193416ce1b761241c2b9848e
coverage-docker-npm
27.6 KB
sha256:0d38815110afce6d152debbc328eca1eb80877051f6757cb61b543558370c712
coverage-docker-pypi
27.6 KB
sha256:4f895bd4d17663e00f084f3fe1d8cd054c1d84dd973666a58956f58fd83e18a9