Skip to content

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

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

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

Triggered via pull request May 23, 2026 00:42
Status Failure
Total duration 7m 45s
Artifacts 39

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

6 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 (windows-latest)
Process completed with exit code 1.
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/
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/
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 (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 (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 (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
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/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 (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~8NXR1U.dockerbuild
11.5 KB
sha256:5ded8a6d27aea47e2fad8bde20626ecc8f7ea8a5fbe3c9f1c80e264a1e6a5621
SocketDev~socket-patch~8OEGDR.dockerbuild
33.9 KB
sha256:4e5161255e6457c794ae46a385517b3d7e869b71dbb39d4c0a6922185d0c4406
SocketDev~socket-patch~BBHM1V.dockerbuild
34 KB
sha256:1cb5c096516c2ef38e0c26c7df4027116b20928e44548bc50da778beb9b5a4bb
SocketDev~socket-patch~BIAVUG.dockerbuild
33.8 KB
sha256:d4747c6af4560525cd45a6a1b00f4745ccf4a6531416ceeb968e05282362c456
SocketDev~socket-patch~BINGBR.dockerbuild
23.2 KB
sha256:913855684303de2b8702a06457791471d16c8f4a4a6471cd67ab32ac4ae83f65
SocketDev~socket-patch~CQ50VD.dockerbuild
34.6 KB
sha256:7675cb21d58d8d902eeb9f5ffc794845969823a9cb87b52e4d0bb8c87b573c67
SocketDev~socket-patch~DBKQGR.dockerbuild
17.5 KB
sha256:a158562476601086e5f844dfb7af3377935a0c18c3bad3c414288fe9a9361a99
SocketDev~socket-patch~ESZV89.dockerbuild
19.2 KB
sha256:4677c4f559d4ffab756f56893319b9f6ab78eb868fb3cf8dc4b9082361ad9c45
SocketDev~socket-patch~FWAI5I.dockerbuild
19.8 KB
sha256:555f2e88baa0784b00b51e6443449f287dab4526e7cd86f31fcef6e61b2acf9f
SocketDev~socket-patch~HU72DO.dockerbuild
17.5 KB
sha256:3fab250194aceaf462cc7621f932a05db2d7053da63a409108faa5103d03401e
SocketDev~socket-patch~J024RG.dockerbuild
16.4 KB
sha256:b57031a0b7706558b3f809288cce0d0fb0c35b4cfad41bb6a62ea55f881f9e66
SocketDev~socket-patch~JATKQB.dockerbuild
12 KB
sha256:bb4ad46fc66624b071660d98ed3a76eefbed89adecf2f784f8f7ba98a08339eb
SocketDev~socket-patch~K6QCVX.dockerbuild
20.5 KB
sha256:1d4450e5046de62ef16d8605bc9258cc46648edf4b1f0f4ee7148ec187f0f41a
SocketDev~socket-patch~K75ZRS.dockerbuild
32.9 KB
sha256:4969e2d157b4b81c370144eb9878f8d257d99438a586ea1a6817468efeaec87e
SocketDev~socket-patch~KUNQSG.dockerbuild
18 KB
sha256:9eb0f5ae676f691e8cdaf86a70527ba141a9a7ee6917dee67defe3902541a0ef
SocketDev~socket-patch~LTGWIS.dockerbuild
33 KB
sha256:c3b6f1a12bf8ee3ca5d5b069d066b865b3e8d4192198f62ed445e99c8ac0857d
SocketDev~socket-patch~MGX9UR.dockerbuild
24.3 KB
sha256:b4d847a9bf5498ac0664aa684d27a41b50b0c3baaa338a0f468b8e7af6b8451e
SocketDev~socket-patch~MH3HCF.dockerbuild
33.9 KB
sha256:b9cf6a36551061a2bbb1597a40d818eb624d8a39c2efd9c2dfca301693eedb8c
SocketDev~socket-patch~N8OSGS.dockerbuild
33.6 KB
sha256:ccdeb650cfb5540da58fed5d80e12807823cf0a001e1ee1a2805f521daecfbf7
SocketDev~socket-patch~OH74E9.dockerbuild
34 KB
sha256:712ac23eb6bceac1747437ac08a7fefbfdc8b36f1fe5f6f97be37080687b9257
SocketDev~socket-patch~QRL0SF.dockerbuild
21.9 KB
sha256:8fa274fad54cde23b27ebba45240645dfc014dfefd2a99230a47b7ceab92cfbc
SocketDev~socket-patch~QVWNQR.dockerbuild
16.9 KB
sha256:626e1f77f6a6962002c867427ec6459ab6569adadd3fddee150da6e8bec29325
SocketDev~socket-patch~RJ0IJQ.dockerbuild
33.4 KB
sha256:ec0e3ffe3d1866c72cc9306392b69b090a407dd042f87626891336455a572fbf
SocketDev~socket-patch~RJ11NS.dockerbuild
34 KB
sha256:fc737ca6b2141d04f0af618617e4b9cf5bba78a15d49911cf9d4921457b5a290
SocketDev~socket-patch~S21LKV.dockerbuild
33.9 KB
sha256:ca82e90671180ea76ca8361dc99243633d3c73ce14c2e743f8a13d60a6f7a4d3
SocketDev~socket-patch~SNQZV0.dockerbuild
33.9 KB
sha256:346dd44a070af2289d494d3a9ee30877922bcde8548d8e5ab090120d162ab100
SocketDev~socket-patch~T4NLX9.dockerbuild
34.7 KB
sha256:99d6b8562c43a1a9762fe95a93422fd5742b7fb6ab870996bd692b4ed36174fb
SocketDev~socket-patch~U5JMM5.dockerbuild
18.9 KB
sha256:c4c1375271c6811adbeaf73c4a3d56253cc9f0d36ac217ace1cd9e555e487969
SocketDev~socket-patch~UVPTAB.dockerbuild
34.7 KB
sha256:ab6548710c92d48ec81b49f860e97975cf4bdbef2ca438454eb02bbd5c2c5a8a
SocketDev~socket-patch~W5OYTC.dockerbuild
21.8 KB
sha256:b26dc1bf36c3948b6fc34a36e2b7dc997c9d55fff9f75cebfb3f8c45e40698b2
SocketDev~socket-patch~XS92F9.dockerbuild
15.6 KB
sha256:b316d08734f61ec8d0d51543812266f8accd7454579cb1205b9bf45430f50c6a
SocketDev~socket-patch~Y17S48.dockerbuild
33.6 KB
sha256:cbea848c0643a4de1593ed5c4e3a90e9b723c7dbbde6a28661cf608e55f5710b
coverage-docker-cargo
27.6 KB
sha256:30e5f82437d040da38007cdac284c9e31dee013f116d35c0210711b7249a14be
coverage-docker-composer
27.6 KB
sha256:0a94fc2615b0cea16ef2806d4c972dfa5f80859f74fb51e04164a6f54090c6ff
coverage-docker-gem
27.6 KB
sha256:24f99a397327be52d86b631999eed927832263cda73689e022b4712651b036a7
coverage-docker-golang
27.6 KB
sha256:df6751a6942365d12d008e6aae8d264e2a8fea328cf30113f1b894e891a26063
coverage-docker-npm
27.6 KB
sha256:1ef169f056f25a0c64bf2408ef2deed88b1361869f1cca90155382df56c190aa
coverage-docker-pypi
27.6 KB
sha256:f87f94740476f2d1e6bdc4c143e7b535dd98401f079217d5391e23020bfb4991
coverage-host
133 KB
sha256:c371a49a6a07060707fc4ff8f2c28ff1aa0846af4abf37e4ddb75040689e0cb0