Skip to content

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

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

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

Triggered via pull request May 23, 2026 02:39
Status Failure
Total duration 11m 26s
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 (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 (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 (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 (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
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~3ABK5O.dockerbuild
33.4 KB
sha256:c317597029dde7344b7c5a314b0ff44c4ecd34a9c9924be88f8cae3191f5299d
SocketDev~socket-patch~6BAPLD.dockerbuild
33.9 KB
sha256:141b478d7a984d71e340d3e98560ec94da724921c16221ab844926f2cc420522
SocketDev~socket-patch~6QMQKY.dockerbuild
17.7 KB
sha256:7f7f93a34e256dd1c4f6c106a9ab6c8c5f48c560bf9f3ebb0c90b00b7cb6eb7b
SocketDev~socket-patch~CBBNWQ.dockerbuild
20.2 KB
sha256:d917ea58f3d7d2924cca23a896e1d01ab7e0fc529cab41799c1c076733778670
SocketDev~socket-patch~CRKPH7.dockerbuild
34.8 KB
sha256:be39178ec538b76880c206334d3e5a5537836f685a01f2d7016bae139f3d20e1
SocketDev~socket-patch~E8VG1M.dockerbuild
15.9 KB
sha256:88b77497c6e7bb50ba1467d18a1afb6492117afb4e60b9825b1f43f4a4abdaab
SocketDev~socket-patch~F1V7N6.dockerbuild
18.5 KB
sha256:7f477d2c43abd723af02d50f2dd9198c54b57182e9f7b0c2f73784ccb1a44f77
SocketDev~socket-patch~HCBB1P.dockerbuild
21.9 KB
sha256:ccb877b7522019827cebe4393a6d45cb933c8be7aa2219a514fb80217dd55c0d
SocketDev~socket-patch~HPC7GF.dockerbuild
19.6 KB
sha256:58f802c147ecd148d042395fb03740acd4c215615af7a798582c5c6a12d3cf4c
SocketDev~socket-patch~IJAT7P.dockerbuild
33.5 KB
sha256:475145acf44c5529a873f201fd2d930ade52f8e4abb64699b05f39e1f1b384e9
SocketDev~socket-patch~JWM8K1.dockerbuild
23.9 KB
sha256:416354e3232c7fd86bf181d62e37bd512d3076896f8a43f67fcfc6bfd741aa08
SocketDev~socket-patch~K0UI54.dockerbuild
33.7 KB
sha256:e97d1f2c89c1f33482d836107013f94bd035122fb75757a4fb74a1bbea3b5483
SocketDev~socket-patch~K3QGRE.dockerbuild
33.1 KB
sha256:1c006248f25b1a1fc4ed5f4365b0b3b18809f58adbda90919bf6fe1eb7a494a8
SocketDev~socket-patch~KE0FX9.dockerbuild
18.7 KB
sha256:5de9f3cc8b15cc222915980bd6a59d7f42833c0cfeeb1275009dc8732451c2c7
SocketDev~socket-patch~KFNFWH.dockerbuild
34.4 KB
sha256:7b97e3b3c1205d791498e4412431ac8c021fc6fa76b9617bbb2ff5adbe0ef892
SocketDev~socket-patch~KN89RO.dockerbuild
18.4 KB
sha256:ae4fec229563f82fcf37242055feb2ecce9b4c431b04c2556b4ca3c4fda30b1f
SocketDev~socket-patch~L7O21X.dockerbuild
34.4 KB
sha256:6393a3357b8cc42048c4806edaf384df95c951a20fce42132c433662584cd8c6
SocketDev~socket-patch~MD12HR.dockerbuild
11.3 KB
sha256:5a6ed0ac181ed1cb7905b84f5b54272076709115c8d00db6d3616655654eef8a
SocketDev~socket-patch~NSI0ZH.dockerbuild
15.1 KB
sha256:005f0aac9959ed56cda073f03c0130a20b7207980ce3e3e86b94366ecd5b845c
SocketDev~socket-patch~OJ5RNA.dockerbuild
11.2 KB
sha256:717749696d85dd53f604499af6959489be20887b07ddcf080475afeb5393113a
SocketDev~socket-patch~P0F0LG.dockerbuild
34.1 KB
sha256:35603cf165c0099c06c0b1c89c907ae6fc9f76765d8d062a0339d9a2131ccbcc
SocketDev~socket-patch~SLFLD6.dockerbuild
22.2 KB
sha256:de6b376d994fbef3a5f4b05be350d30891b52723eab73f5582e4114ad0368a3c
SocketDev~socket-patch~T0E43S.dockerbuild
19.2 KB
sha256:313df4a0d1305ad6d8710c271be784d29ae53121e5603054f9ff9411a1bfeb48
SocketDev~socket-patch~UB2HYU.dockerbuild
33.4 KB
sha256:3f97ddbb243d717ff50ffae787828a42ad129074ca1f75dfff7bb6c68b9de98f
SocketDev~socket-patch~VGF18L.dockerbuild
23.2 KB
sha256:a758784baea2d6c4720e1e0d8ab3217ddf22721a6c86fdaeff044d55b7a5d824
SocketDev~socket-patch~VRB4CG.dockerbuild
33.6 KB
sha256:c11fd258b9b02bf0e317bc59d926a5735639dfacc7b7634ba79b287dc0ae2743
SocketDev~socket-patch~W388VN.dockerbuild
33.4 KB
sha256:e5650123afebd9c354da254fafbf189dcf4edd69e61392c030bb5d44498dbd5a
SocketDev~socket-patch~WDW89Z.dockerbuild
34.3 KB
sha256:ec1a5dc21a4d0d4522615751a385fd87dcc183d51a6448a834df309be0a705c6
SocketDev~socket-patch~WO9BW1.dockerbuild
34.7 KB
sha256:75e41c91494faab0734c5dd256dd7ea35e1f31129cca3e4311d11c7cc4ac82ba
SocketDev~socket-patch~XE8RIC.dockerbuild
14.9 KB
sha256:4b56e6da99836d3ec4019c0a17d54a42b0a5df6bb24ebbdc2f00f818a931f4f5
SocketDev~socket-patch~XZ5K6M.dockerbuild
34.1 KB
sha256:25a0feed82da4cb1c96c67104fe593ab5145fee3c14025f3a124774e033dcc80
SocketDev~socket-patch~ZAE25U.dockerbuild
33.3 KB
sha256:4b07c086a0a0476f6bf6f2c82adc6ef54dd22186025c0d07fa86e41709cb6123
coverage-docker-cargo
27.6 KB
sha256:384a15a36f3016e42acb117e72d147fe3b76dea4c5905d1ae065753a3bc87dfd
coverage-docker-composer
27.6 KB
sha256:3d777391d3d51830b1d77038987c9ac172a38c227219ee011ee75ba7e0500c27
coverage-docker-gem
27.6 KB
sha256:89772630fdc24d05d575b7549b765aa7f71f399ab53d8e4e2548551e1e70172b
coverage-docker-golang
27.6 KB
sha256:86ef966881672a58fba6a3d29b3f0cc1ecff70bd2f9b5e8c2c068f68d6892362
coverage-docker-npm
27.6 KB
sha256:38e9058032ca3bc3f79c2af798991df34f1ee277b3ca63c115a1a85dfc85fff2
coverage-docker-pypi
27.6 KB
sha256:3b53b8d9b5db415b152270638339a35a7e4c5475b9f11b2fa02f66040a296f3b