Skip to content

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

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

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

Triggered via pull request May 23, 2026 03:13
Status Failure
Total duration 14m 20s
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/
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 (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 (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 (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/
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~1GZZWQ.dockerbuild
33.9 KB
sha256:0a9d2b27a9de9c52f405ba5910c3efb2d78e26ac9e7f0f160254abeaf5d6b626
SocketDev~socket-patch~2EBU17.dockerbuild
11.7 KB
sha256:47c6f8f4b201bb432cea3f9f8b84a178975a87a4a15a40561d96e44a97d2d721
SocketDev~socket-patch~436H7X.dockerbuild
34 KB
sha256:2ef40f76d1198de386aad49e36928c49aefd6fdc4597ea5b3d4c286ef0a6825c
SocketDev~socket-patch~4EV2JQ.dockerbuild
21.5 KB
sha256:a483beaf76e4250bfba3626e5801242cde7225e5ca0d6e8258c17bd6de1a0083
SocketDev~socket-patch~4K64GK.dockerbuild
34.2 KB
sha256:6a04ca465ff956a2e9072beb3658634403180bad38a8941b299acdf7aee8fa50
SocketDev~socket-patch~5O9WJI.dockerbuild
33.1 KB
sha256:ecda15e79b4fb91a08ccca26096647e426175f2db5274062b1f22ebeea160b8a
SocketDev~socket-patch~5VUILX.dockerbuild
18.4 KB
sha256:069671521a49f315df2d2d6217c30a7c25c76c4250dbd57a35a13602d195dba0
SocketDev~socket-patch~65GM0P.dockerbuild
33.1 KB
sha256:baaca1da37dddd651920156701b223453373cd649f02249c5ecec6697d0f2c3f
SocketDev~socket-patch~85UPF8.dockerbuild
16.2 KB
sha256:b122320846929697a5721dfda57c48c473e5a8f5c77e2d41b0e6e1b38fcee37a
SocketDev~socket-patch~9J5AVR.dockerbuild
18 KB
sha256:d6624999bbe5c382165c209be3d89fb159c154fa6cfe6bf6868f4e289b1c3de6
SocketDev~socket-patch~9PKIBM.dockerbuild
34.1 KB
sha256:21a4e631458e914acb1e5f0098613a2a7fb859083e5a670b4408561d12a1de58
SocketDev~socket-patch~AVOE4B.dockerbuild
33.9 KB
sha256:1bb61f22c2f6e322612f78bfe3c6a94cdc727bda048e1a39088996ac858df446
SocketDev~socket-patch~B9N9KC.dockerbuild
32.8 KB
sha256:28e6bc541ceb3544f662feaa9fb387c57ff63541cb1c78929eef654bd752c687
SocketDev~socket-patch~CAX5ZO.dockerbuild
11 KB
sha256:33768a2c34767e43d0f00907132408aec0793b318b10dced9b95a0c71ea0a48e
SocketDev~socket-patch~E7NDQP.dockerbuild
33.8 KB
sha256:ee244ab80556d5441ef01011eccf44761d0c9d0afd3efda45da8a7e7e771221b
SocketDev~socket-patch~ENNTP8.dockerbuild
15.5 KB
sha256:dff782a1e228d16b9c2bec951dce1d3e1d994ed884ff537694bd22f684da7ef5
SocketDev~socket-patch~FFYCAX.dockerbuild
23.8 KB
sha256:c36cdde7e5dca4969cacf2b8222ef7f8cb1a76911e18d187151b68ab5b54ede8
SocketDev~socket-patch~HX33YQ.dockerbuild
34.2 KB
sha256:d7d6a17683ab0874a7bdfc04de68bdc874046fa441af09b825e0c2f635d8ca6b
SocketDev~socket-patch~JKCDL1.dockerbuild
18.1 KB
sha256:6fc8b8a2955af5bc0e772be2c42a9c11e07dab400ae3d0f76c05f8d75d712db7
SocketDev~socket-patch~LP2AO5.dockerbuild
15.9 KB
sha256:664c068b8b3f69a8fc0673bba471ac0a0451f4fc282bcdbfeec3915ef0b3b474
SocketDev~socket-patch~LQBQ8U.dockerbuild
33.7 KB
sha256:82b7acc61aabb5872149bd93cf0554facd866bb33d771579683294b0005b7fb4
SocketDev~socket-patch~NEPRSZ.dockerbuild
19.1 KB
sha256:b9e526ce6d94d0bf21439cb346da7ccf9e7321aa5a576fa54de1548373a68942
SocketDev~socket-patch~OQJZRT.dockerbuild
33.4 KB
sha256:fa005084ab560d5f04f6cc2d728938342e7a55923219c45991b8847c111e3fd5
SocketDev~socket-patch~PQCV91.dockerbuild
33.7 KB
sha256:1bff334931d17c32c570c96aa0d575ab16f1c0b857d7fa2c6095f9fdff50e463
SocketDev~socket-patch~QH721S.dockerbuild
20.5 KB
sha256:6ba0f60181f48b2b114c8b05666234de82719938648335e743d24be857a353e4
SocketDev~socket-patch~S5QC2W.dockerbuild
34 KB
sha256:22813caf4c248341357b94985b3933afb19c3aa58e6fdbdf8bb45c514af446ca
SocketDev~socket-patch~S6CUSL.dockerbuild
33.8 KB
sha256:5df09c467e175b035c21d019b57998614836cc135f885ab9ed11eae7d698aee8
SocketDev~socket-patch~TCPWQJ.dockerbuild
33.1 KB
sha256:5d18799dec3631381a46bc180144833fc3fbdd4693d8358f892668e4567aad6d
SocketDev~socket-patch~TJU9PA.dockerbuild
21.7 KB
sha256:27891820ed3ceb69c54a5029533fe0c6a49d32b0de7cc3be78a5c4907f0e1ddf
SocketDev~socket-patch~TLHA0A.dockerbuild
18.3 KB
sha256:67b42830a13f43aaeb96d62990376c2c9057488974b9b8ed9ab428bc2f73cf10
SocketDev~socket-patch~UI7EO7.dockerbuild
19.8 KB
sha256:7952aa6037a7667232304a5eff229c5d9f982bf1c08533132a149e09bc2b6723
SocketDev~socket-patch~W7D5R5.dockerbuild
23.6 KB
sha256:8c746c5fa45aa257ccb7434007f2a3244df8d4dc47542a1f46d5450d7709d26a
coverage-docker-cargo
27.6 KB
sha256:a195943d149622ca9e7a5ad4f5a44c21ebceba8aefc5bb6993c494d41697c175
coverage-docker-composer
27.6 KB
sha256:cc395a9c9e3915fb6244cb6b870dca7ea4805daebf83cae59184fdc4c99b8c5a
coverage-docker-gem
27.6 KB
sha256:7cef631f0b4eb603f988055f5bbdca85f50affef8150e6102746b095bccbe201
coverage-docker-golang
27.6 KB
sha256:becefd17498e68fb22818c5324b04c0efe6d2103ab5eb607d2b83477ec69ce89
coverage-docker-npm
27.6 KB
sha256:9aee631eb1508aa455423b92c308a65a4efebfcf538f861c5ef5ef340ed58a1e
coverage-docker-pypi
27.6 KB
sha256:42038cc580b23aaa72f68899e7b2b9f9effe1c462b45db1a40fcde6b71655a8a