Skip to content

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

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

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

Triggered via pull request May 23, 2026 03:53
Status Failure
Total duration 17m 7s
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 (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 (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 (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/
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
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 (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 (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~38RUD9.dockerbuild
17.7 KB
sha256:31c43d6e26c3b0e336b7a78b2831fc5b314c1a475debf52ca883dbd452fa2eda
SocketDev~socket-patch~4IFXPA.dockerbuild
34 KB
sha256:ffd13e3755476ff7f265bb8117bb1d998f9b569fa847f1f3084198dac24d8832
SocketDev~socket-patch~59VNWI.dockerbuild
18 KB
sha256:d4bba0f86da8101505ac54b2394cc2cc57f49040acd271a9be17508090a1dbe1
SocketDev~socket-patch~74S8Q5.dockerbuild
20.1 KB
sha256:5e638a752fc6c110e12044c27f7721326f8e98d025055e3e535c84a161099da8
SocketDev~socket-patch~7YQ0W6.dockerbuild
15.7 KB
sha256:77a5636a088a4719de66189eb0def584d168ce743b5c269e1565196f2e4be586
SocketDev~socket-patch~8IQFC8.dockerbuild
23.5 KB
sha256:1ee10b4f731e632d91e286bde1d22f965fdb7d0e72ae35ff9de795311f13f762
SocketDev~socket-patch~C7POX3.dockerbuild
11.6 KB
sha256:6a5b11794e76004dd06f001c72256b67918fb0ad8e3f5b8d3313562c8c1cdbee
SocketDev~socket-patch~CE9UPC.dockerbuild
21.8 KB
sha256:efd1cc04dc295c5bc0bf41fc633511428b26833fd34361ec59867d57a68f6516
SocketDev~socket-patch~D1ZLMM.dockerbuild
33.3 KB
sha256:dd7ad1dd683c2e2422dc9c6863b7e7eac7d108d371d03eac54e8096ba93f8e2f
SocketDev~socket-patch~DFWZ81.dockerbuild
17.7 KB
sha256:7f6a3cc6621e793abd1870868ad0ccc2ad546626f64c330fdafc97714246cbdb
SocketDev~socket-patch~FCB7H8.dockerbuild
17.5 KB
sha256:072ef484bbddf0d256f4704971ec4c44c8fe7365f9e4e553fe5ede55bfa91f81
SocketDev~socket-patch~H6N1KB.dockerbuild
20.3 KB
sha256:809f914f2d14825ec78b2206dd669eed066a1f86585031777f79c3ef57c6dcd0
SocketDev~socket-patch~J047F3.dockerbuild
34.2 KB
sha256:6075da2d00e09e4b2ffac61f36c9f60e730b14a218111e5f8c6bf496e29b7dbb
SocketDev~socket-patch~J0SGTE.dockerbuild
33.5 KB
sha256:9bf9aadb04fe004730f2d1d9dbbf1d914e4a51e74a3102044062bb36a1fd36c6
SocketDev~socket-patch~KW88XE.dockerbuild
33.5 KB
sha256:71a30d59aae781cee0211c23ce1857bbd862f47aad1b98ec5eb34636aca377be
SocketDev~socket-patch~N7TKFY.dockerbuild
34.1 KB
sha256:72fd3a3732a7eb17e04ab075b990c65ddc1fea9b19e80879d08cbcb5d21249ad
SocketDev~socket-patch~OJ8KOQ.dockerbuild
23.9 KB
sha256:81abaf6588ec1e455a119221b7781aeb32c2cce98e9be103d8e42d82adf8ca0f
SocketDev~socket-patch~PEYLPP.dockerbuild
32.4 KB
sha256:e0b59bd12264688d1f8bb5955b07e7eb980a353baf3e0979b681ccfe43c1df04
SocketDev~socket-patch~PG0TBO.dockerbuild
32.6 KB
sha256:c2e2a3ca951b4533372ef809a7e921ab4c0babf7a14a6f1457ee152fce0821f4
SocketDev~socket-patch~PL9M17.dockerbuild
16 KB
sha256:3d36760ad6c86c94891260e145c193e774db055c196305df340828cedd780236
SocketDev~socket-patch~Q4NWZG.dockerbuild
33.6 KB
sha256:f3304386c32f914e6280ec8bf5e64b6a0842449d82c72faf2c8d8095e80238c1
SocketDev~socket-patch~RDMBEC.dockerbuild
33.9 KB
sha256:2a807e988b295e051d40ddc6653385a8e6d77a93e8ad982886cda7c9bf8284c5
SocketDev~socket-patch~SI4C00.dockerbuild
18.5 KB
sha256:64e7c6c000413bdcc9296b144e41b52232bd0ff05cf5611ddeac74f59fd4bf48
SocketDev~socket-patch~TJYIN9.dockerbuild
33.9 KB
sha256:735345c4fc724742dc32edd2ee1d9ef9f1f646d5d18bc0fbd0d1ce51ac16fe20
SocketDev~socket-patch~TJZ1QI.dockerbuild
34.3 KB
sha256:7c8837be8a01bf322ea4c74b61a73b7bd99604aa6aee9ea028bd593aac817c38
SocketDev~socket-patch~VUDAK6.dockerbuild
18.6 KB
sha256:9ced52287e7ec1e956f8f086044639c94dba7f3d07b2e84d2fdb77958b54202c
SocketDev~socket-patch~W2P6L4.dockerbuild
33.9 KB
sha256:d1b7e78eb4de8191f9ce553e4a9b605c088e20115fb7df38083ce253058de557
SocketDev~socket-patch~W33NTD.dockerbuild
34.9 KB
sha256:32c5a87b742a659384ba459b74842e96393aeabfea0a3f03d1ae3150222487fa
SocketDev~socket-patch~WIO8I4.dockerbuild
10.7 KB
sha256:adf87ddb4d024bf9fc422b600abb8a80853c508b9aa4c0cc05f300833304853c
SocketDev~socket-patch~WV5DZE.dockerbuild
22.2 KB
sha256:7c3d7d8a7864579ead47517f3caf04961bda70aca5c30cddc814dab5c1167bb0
SocketDev~socket-patch~X3B4WB.dockerbuild
33.7 KB
sha256:c537692ecf15ef672722c51eab64f31223b3a0802fb2acd150aa1979da23efae
SocketDev~socket-patch~ZZC3HC.dockerbuild
33.8 KB
sha256:a59b7c80fe76de194e33bfc6bc98fddb063f5490f18d1cfbed4b721845a91409
coverage-docker-cargo
27.6 KB
sha256:1a6a543aeb4fbd3cf6fe37a011f06dd4dccea924adb1f86edb1e8bab84beb61a
coverage-docker-composer
27.6 KB
sha256:6525f4305fbe5b93290fb906fb3857ff940dd32df7db1b04dac1a3ea45ab8114
coverage-docker-gem
27.6 KB
sha256:13a00748e476bdfc5ce12d592e3861e40ef3575db4340e0c1b227fe1993a1d49
coverage-docker-golang
27.6 KB
sha256:e316efb110900acfe22d712eab20b492000c7b750f2b729c718bbf18c695b0ee
coverage-docker-npm
27.6 KB
sha256:bd865f62154bd7d0c43585987f5f687f2e9947bc2da52770b62c14d508b8c3b9
coverage-docker-pypi
27.6 KB
sha256:9c2a46e1daaec6c4449be6efafdec2949e372e54b1f440dbcc4dab62b6b2b3bd