Skip to content

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

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

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

Triggered via pull request May 23, 2026 02:49
Status Failure
Total duration 12m 45s
Artifacts 38

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: e2e
coverage-merge
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.
test (ubuntu-latest)
Process completed with exit code 101.
coverage
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 (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 (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/
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/
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 (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~04NO7S.dockerbuild
33.3 KB
sha256:6a9340b93751b010e6535e927622d220d42e8afe03fdd88475a089d637d9b853
SocketDev~socket-patch~5PB827.dockerbuild
23.3 KB
sha256:c891cf97d35c98323c5d8e30f25bfe8311694765c97dbec3177d25c4890070a5
SocketDev~socket-patch~7PC8EQ.dockerbuild
15.6 KB
sha256:0bbb37fcbe4123119ebc93035b503732fed6139d72a0b654fda7c59aaaae7bb8
SocketDev~socket-patch~9QL7J3.dockerbuild
10.9 KB
sha256:baa3cc02da7623fa09edcf603058de411a6d8d95c2a05282eb4013c961c25672
SocketDev~socket-patch~9QO18T.dockerbuild
33.4 KB
sha256:d613802f3aa9c049fa0eb1a1632fb51a11eb6072d2ee8ed5de74dd7bd2faff88
SocketDev~socket-patch~ASK908.dockerbuild
18.6 KB
sha256:5f7651f590ca1c44d05eecaf07cbe4bb0c0725a0ee4b785b98b3ce695c8cb980
SocketDev~socket-patch~B3PZRK.dockerbuild
16.9 KB
sha256:ea0b980374374af103d01c075ad74db8afc452ce6c0f57a84159792dea5427bf
SocketDev~socket-patch~BA2HNW.dockerbuild
23.7 KB
sha256:eb6e15af85f5c488d95d63ac5ad21967fe402f68fc62d7fe150abef2b72bc7f6
SocketDev~socket-patch~CUFKN7.dockerbuild
18.2 KB
sha256:6f8aa3fc5eeaf92c65739fdb6534cd4bb2d25c7ead82076416304389a3d57128
SocketDev~socket-patch~FS7U69.dockerbuild
22.2 KB
sha256:72c7ac2a6722deef682e79599a4f907f84f10ae285f26ae88bfc168dc8147924
SocketDev~socket-patch~GXA2UJ.dockerbuild
20.5 KB
sha256:7801f7d8fa37968fa08702bdab1dbd9d1807a8117543598c489c50f574b07650
SocketDev~socket-patch~IWLSDB.dockerbuild
18.7 KB
sha256:2cf4bf32adfdd2813419e01f390afc6913c4105db0b92b69c07b09628f4b76bc
SocketDev~socket-patch~K9VLML.dockerbuild
34 KB
sha256:2553636e2c48b9509eb04338c553f7e6df68b0b4ddbf9dfde73fed1814d19141
SocketDev~socket-patch~L68EU1.dockerbuild
33.4 KB
sha256:ad075a533b076cf28e8e4ee23e13fefbcf22db22ff86429af3b114b8c5e1229d
SocketDev~socket-patch~LW75WI.dockerbuild
34.5 KB
sha256:9c37367287d038cce7788f84312b262c124280990d8793e9e993348e12cc08ec
SocketDev~socket-patch~ML1TIW.dockerbuild
33.3 KB
sha256:089ca0ba240388cab2990e310d07e021eecdd384e722eab4398a28a4921aae6f
SocketDev~socket-patch~MQF88Q.dockerbuild
33 KB
sha256:8fea72f424bf716943674bd37b36ee38039de5112aff7abcdfd288149e2cc8bc
SocketDev~socket-patch~N0I41W.dockerbuild
20.1 KB
sha256:86294d4651479f52d88c64ed2dde62624c417be66ec02c227dca8a785bc7a7a1
SocketDev~socket-patch~OLZB0J.dockerbuild
33.9 KB
sha256:23be8557e18963fbabec085d2e50250f33c7fb2b79856a282a4887f2bd7b7792
SocketDev~socket-patch~PD6XYH.dockerbuild
11.8 KB
sha256:d2fe68e732eb425460b1cd07d0f5fe67047118a4dc631e680b6bee9d0710ebab
SocketDev~socket-patch~Q4Y1W5.dockerbuild
33.9 KB
sha256:0b6ea925766d69fe34f3aa3f15df36e87e1c63d687618fad470e532b8d0c72cd
SocketDev~socket-patch~QH4V30.dockerbuild
34.1 KB
sha256:deb243dc33de424b734a529026857681f56f11a287581d98be6a9f1357d0b958
SocketDev~socket-patch~RI9NBC.dockerbuild
33.6 KB
sha256:182cc728ef4713f23259200e50b382e8c85e1f4b34206a785bc4cc53762b9e6a
SocketDev~socket-patch~RN6JJS.dockerbuild
33.5 KB
sha256:4cc651b6e188ce375476ac41f4e2dea03c7f1da6b5b4c747d2d897c146772067
SocketDev~socket-patch~SRJ5FY.dockerbuild
17.5 KB
sha256:1e954784ab982264a477f3af0933852473e6679e296360ed333a1957355646c1
SocketDev~socket-patch~TZ96SS.dockerbuild
15.8 KB
sha256:95885570a73522c9043b5d36360ec0f51d7ef294441a9d344c00ee45d028bc24
SocketDev~socket-patch~VCVRPH.dockerbuild
21.6 KB
sha256:7703e4a8a23d10783e22d4f7fcb0297e2c03301a39f617950fdccdd456bf1b69
SocketDev~socket-patch~VEPG6E.dockerbuild
19 KB
sha256:71e8b1bf4a64ada2198758a1ed74b7b9faed8340e3d57033cb3dd790bcdaf33b
SocketDev~socket-patch~WK15M8.dockerbuild
33.3 KB
sha256:caaf49b710f99a182c60efe3408a0a7729f671d759001a3757a5e9793967528e
SocketDev~socket-patch~XBECP9.dockerbuild
33.3 KB
sha256:4c92aecd8ed55e047dd05782d4a9854b98ac1e9c7e20cb5a335b0c17d8c674d7
SocketDev~socket-patch~YR68N5.dockerbuild
33.7 KB
sha256:90323a08e24aace5736eda4abad3b84343df391d74c4a7025351a9411a1d0ba0
SocketDev~socket-patch~Z4O5RD.dockerbuild
33.6 KB
sha256:45525a74dae96c232661d00b394ce986ebb9063761de1ba8b0f95b51577fa96b
coverage-docker-cargo
27.6 KB
sha256:e9721e0deb11680eea2aba6d1b50ada4b55ec4294ed05ed369788610688b481c
coverage-docker-composer
27.6 KB
sha256:23e45c80dacfd9d6a3ec2325d6329e3d182df659d1963cd2e658a259bc9c848c
coverage-docker-gem
27.6 KB
sha256:a85d0478ef485e092fd049119b2256f09e34ab19cce11c71b83e30d0581c165c
coverage-docker-golang
27.6 KB
sha256:19e22d52a3dab53acddcbbe2d1e0d5a8e5f734f4f3892564339937a44924e62f
coverage-docker-npm
27.6 KB
sha256:67995d4fc610d80e827cb44cd3fa9f3f54d3dbb298561582bbfd2484168e799a
coverage-docker-pypi
27.6 KB
sha256:73295492d136f1cd968e6484b30138ae033bba4724e06269a401655f7acde1c9