Skip to content

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

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

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

Triggered via pull request May 23, 2026 12:21
Status Failure
Total duration 18m 26s
Artifacts 43

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

10 errors, 14 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 (macos-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 (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 (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 (deno)
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~06M1SQ.dockerbuild
34 KB
sha256:ec328e8cf051b599dbfcd3c12f5ed8b9dab7a753dd57a22c8e00e11f601090f3
SocketDev~socket-patch~0986MY.dockerbuild
34.6 KB
sha256:2c85a3b03b20ac41f511d89a6c8b571e76949a2cae6d05e1909047d52cb8db2c
SocketDev~socket-patch~591LEK.dockerbuild
20.2 KB
sha256:32e510bff615a3a4feabbfb21f1f95793333f24021196fb534a6e5ded83e6edd
SocketDev~socket-patch~86L1ND.dockerbuild
33.8 KB
sha256:8d334a4f7ebad3149cb38ac197dce4f70afa2a0116fadb96e30e7ad52f7e0dcc
SocketDev~socket-patch~8RGDNS.dockerbuild
20.2 KB
sha256:3736078a7e67c32077042135ecb3abf34bdd8bef6e7017b90dde38dbbcf0b9c2
SocketDev~socket-patch~A48BTV.dockerbuild
18 KB
sha256:b9a28676189da4d9866a24a260d18bf6e03d8c3d31aabfbf9f2bdb7fa54ca212
SocketDev~socket-patch~A5I8DW.dockerbuild
34.4 KB
sha256:3d3882aede6ce894672ae9849588ae7f2fc482866ab3343565f758d070a0d5c6
SocketDev~socket-patch~C5UWIM.dockerbuild
12 KB
sha256:0e4ff3ea6eb0dea40aac4b51ce2cb20453c2205bf7c55c466b5bbe8ec837d504
SocketDev~socket-patch~CI1PQ3.dockerbuild
23.8 KB
sha256:88fc93cf6eac55ed55a28f32387c6f92fe0bcc72ea8418d6b938a3fe32ee8c0d
SocketDev~socket-patch~D4R2NQ.dockerbuild
22.2 KB
sha256:593fab6a73ff94f8c82616164452ab6715f14c3b240fbc2905d13ab21a35e7e3
SocketDev~socket-patch~D7DPRS.dockerbuild
34 KB
sha256:3b71c6cd7bb400bc3cf79492447d536f15a5e1b5b49bd4966296d3fc05f8dcef
SocketDev~socket-patch~ERETWA.dockerbuild
17.9 KB
sha256:2583b310fb3b6ccfcb648618f5b07d793a908928d5bd1a4a6c7c7a05f06ee158
SocketDev~socket-patch~ITBOJ0.dockerbuild
33.2 KB
sha256:89d51144c7ce8373f9e51d2786fbd0dc709669c28366af658e3fd04637784e6b
SocketDev~socket-patch~J5XWUP.dockerbuild
20.8 KB
sha256:fc0c3896ab1f8ac0480cc4cffa0308dfcd5259b0e73911a2e22f2660933a8eef
SocketDev~socket-patch~KDK3SA.dockerbuild
33.3 KB
sha256:c7a7103e82a961bd1552b4ac1816f5eb545797c618e55afbef245bd0f0599f80
SocketDev~socket-patch~M5SY1Q.dockerbuild
20.8 KB
sha256:62d6c5443ddfab24d1c4dcb63a8dc8b6daec3c6bfb3289dbc2cfeb88d58b1cea
SocketDev~socket-patch~MV38N0.dockerbuild
17.8 KB
sha256:c862ded2953093d023d9b159e67946f1e28c040d38a7b12c0e19775465372e01
SocketDev~socket-patch~N1WGTB.dockerbuild
11 KB
sha256:3322500650dabaf13433fcf33631e5fdefa063b471d9b297ffb3d0e03342677a
SocketDev~socket-patch~NMVWNH.dockerbuild
33.8 KB
sha256:9c074e9f33bac5d30478a9c4fbf5adabd24c5815cd578c5b163d9a50c7068227
SocketDev~socket-patch~OPPSVV.dockerbuild
35.2 KB
sha256:65e1df18ab29ec383ce589105b9c7c120f3ae5ee3aebdee1d054d3486269540f
SocketDev~socket-patch~OSGA3Y.dockerbuild
33.8 KB
sha256:4bd24631c1d8f84724ba29e0d0438f5a0eda1ef3f16b8f384ed6565c8e672515
SocketDev~socket-patch~OWHVV8.dockerbuild
20.8 KB
sha256:b5f186a8e219bd8eb25ec93c71b38febe4a000e99e3859eeb98379338b5ac26c
SocketDev~socket-patch~PXB1WG.dockerbuild
16.6 KB
sha256:83c36368692b014506423dbfa393b5cce49fee8813a95cc8af3bf01d84d75358
SocketDev~socket-patch~QKZWIT.dockerbuild
19.8 KB
sha256:3f7a36d9130157c6d397db131be0a199640c78cc30681fc73865ccdb5f9295ab
SocketDev~socket-patch~R6D67W.dockerbuild
16.1 KB
sha256:b898a3d40a31d4c7b9c5ec16156066b7ea1f7137dcef1bd630fd0fd2e827df59
SocketDev~socket-patch~SD25XL.dockerbuild
20.2 KB
sha256:55c635012a83c81c22a27db9ae0f4e8d071061db36ce5a58e84b2e430f241c96
SocketDev~socket-patch~SSE47Y.dockerbuild
24.4 KB
sha256:5c0f08f36189a2486c75d5f81fed36e0685652716abd890a3c7220f256296996
SocketDev~socket-patch~T30FEV.dockerbuild
33.7 KB
sha256:88cc970e1377113814e89c951d992e598527b8426f5722088ed0874c16e188a5
SocketDev~socket-patch~TG8R96.dockerbuild
33.7 KB
sha256:4c9a52467e8db483fe8168c5995ed63fc4b2db8ce2f2b0b24046653b522bd4e1
SocketDev~socket-patch~UVWJW8.dockerbuild
33 KB
sha256:e9ea9fc348cdc2bf94de57ac101ed844d61a4761cf0488086b444222419cd2bf
SocketDev~socket-patch~W2ZAVH.dockerbuild
17.3 KB
sha256:8333bf13cd4e58fc06a0226f54c26b18893cc5e56d06e267c2465c7fcb4da05f
SocketDev~socket-patch~W6TGZ6.dockerbuild
34.1 KB
sha256:2886353ebdde922a07a9aa5130bd8fef7276860e02d02fffe37104055b879a46
SocketDev~socket-patch~WAPF9N.dockerbuild
33.7 KB
sha256:992c9e9335af12b3951af1d12cafe954966971008c6211ee80cce8dafeb2383a
SocketDev~socket-patch~X0VCNN.dockerbuild
34.3 KB
sha256:740b45ffd55e415c77d9c7d25c6945795c059495df6141afaf68bc01410997f9
SocketDev~socket-patch~ZLB5Y4.dockerbuild
33.1 KB
sha256:27c60b9fad627c1e1366b06c26a5623edea01a66fb000fabd7e8b41743329536
SocketDev~socket-patch~ZZFSTT.dockerbuild
33.7 KB
sha256:19aa3022a60ea7efe9ac4ef344a909ddbc9275ffa7ea07a573c3db0e4edac282
coverage-docker-cargo Expired
28.7 KB
sha256:af44257f05e58ad29406a574558ae79013dce3da3b802a2212b3379682ef81e0
coverage-docker-composer Expired
28.7 KB
sha256:1cd5187a99ba9d4df38d66c253c324f4fe2f3310ab6e190c1f00784026e5c78a
coverage-docker-deno Expired
28.7 KB
sha256:b3f7eb98fa5c4d2c89b78931d178751bb0c20b1def8789ec20230ca1cb753c8f
coverage-docker-gem Expired
28.7 KB
sha256:6f0ec08acd74f8bbfa88f4d6b567ba83a0ece206657507b6a3dbe69826fe8e7b
coverage-docker-golang Expired
28.7 KB
sha256:5eea749bd318f7bced2efdf5db498c914890ca63a4e4cb09ef2365bdd3c4d0b5
coverage-docker-npm Expired
28.7 KB
sha256:9e7e4bb9955043149ea2112f5d094d3da541ef0e9b7519b0769ab6c818dfb289
coverage-docker-pypi Expired
28.7 KB
sha256:2e711e2f6241200d97cb573fe1a9ede9162ba8133ca1ca7b594763e6cbfadb53