Skip to content

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

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

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

Triggered via pull request May 23, 2026 00:45
Status Failure
Total duration 10m 37s
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
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/
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 (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 (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 (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 (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/
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~0TQPI0.dockerbuild
33.8 KB
sha256:54f4c079c733d3add0649e865592d9aeea8c7a374e39a05b35f91f03570d693a
SocketDev~socket-patch~18WBEU.dockerbuild
34.4 KB
sha256:15846b75b68427eea967c087841e03c00f7f634a750bf48cedf37ff759d6a92b
SocketDev~socket-patch~48VHWQ.dockerbuild
33.5 KB
sha256:9a6d9a3f036e5f98e7b82109e4125856352291063e7728339bf669b6ab4d23c1
SocketDev~socket-patch~5LN8MA.dockerbuild
33.9 KB
sha256:fc3ae8c0c1d6c8d1a65909a340e5a1b2a70deb7431974c43bec8a21a6eb20c2d
SocketDev~socket-patch~6C9BLS.dockerbuild
15.7 KB
sha256:08d618666c1398f87c64c55c1158eca5c83d9d15f0b5eb9a321dfbfbeab0390b
SocketDev~socket-patch~6GXWI0.dockerbuild
11.9 KB
sha256:02dbba1efdf31cc4048fee10424a7af6e64ff5216078a183acda17ee77cf3461
SocketDev~socket-patch~7KKM3W.dockerbuild
32.9 KB
sha256:4c2c56a5ef33c5c5cf846b9ddbd88e6c568000469e9777cf35336f50a7a7dbb5
SocketDev~socket-patch~87MOUK.dockerbuild
33.6 KB
sha256:7fa41c1a109597ede63ddc4f5e95e42f91a133a8192cf09162cb91cd37e3b6aa
SocketDev~socket-patch~ARE0IF.dockerbuild
33.8 KB
sha256:ed5bc69b4080134594fecc369b58714aa0b5356dbb853d2543ab2722707666d7
SocketDev~socket-patch~AV3KYO.dockerbuild
33.9 KB
sha256:3ca52f6248bb7a39629cb72a4fa3ef1ac607e2b3bd11fa2a9c61283e466a16b0
SocketDev~socket-patch~DUMJTE.dockerbuild
34.4 KB
sha256:a1df9649c382ab8c02ac1419f8d826ef8aea12695c3c4fc9c1993556ca9d1dd5
SocketDev~socket-patch~FJLCRV.dockerbuild
17.6 KB
sha256:e605bbacc8e4391dbd7e02a5c7188c47d0b02cefa50d50274fd9e790e8f18270
SocketDev~socket-patch~G9VHR8.dockerbuild
20.6 KB
sha256:2d0ce43f0dce1976e46ffff442b6ad3711dd14c3f6e6b535a2e725a1da949939
SocketDev~socket-patch~HWQNPM.dockerbuild
18.3 KB
sha256:56ba2c938fc96cd956d0cc0cbb11ee511b39fb63d1fbd83d267edbf2d9a0d785
SocketDev~socket-patch~JHW4RG.dockerbuild
17.7 KB
sha256:84e736f77e72bd4f04dcee23755135a171be01216463e3a3d35cb3ea99944030
SocketDev~socket-patch~JLZ5P8.dockerbuild
15.6 KB
sha256:529e56389998eaf83d109800df26d162664911fb2ec1b6437448113589acb81f
SocketDev~socket-patch~K8H5AX.dockerbuild
23.6 KB
sha256:2352fc9c31b1f111c6d316accd8f084211633441cbf816decdbb90feab22c7fe
SocketDev~socket-patch~KLV6OZ.dockerbuild
34.8 KB
sha256:bae6fda790aa1767ef270f6346f30b352135664c8399ee4087077e5ddf700250
SocketDev~socket-patch~KPRS0U.dockerbuild
33.3 KB
sha256:49746d1c3ffc4f85d1eedce1dc2f8a80a7c26c45db716899838eb058ae628bce
SocketDev~socket-patch~L5BMTK.dockerbuild
11.8 KB
sha256:d01bef85ff1e8df6270f52a8098da437e6468329c47338593c74e0859fbf7055
SocketDev~socket-patch~LECU2Z.dockerbuild
16.8 KB
sha256:11c257f18f757c25295290e089b243b6bcf3d26130cb222768305a868b953b61
SocketDev~socket-patch~M54T0C.dockerbuild
33.3 KB
sha256:ba781f4eb7f346f7b49f2a08ae45fa2f8c88645f181bb9fefb634e74e78f42a4
SocketDev~socket-patch~MF3FFD.dockerbuild
20.2 KB
sha256:0c2adeb66bc89b94570bef9536381ff6a37cc0b390a6d2c70be5a94a0fb06434
SocketDev~socket-patch~O7UJXT.dockerbuild
22.1 KB
sha256:894bd312fc20d0ea332d3b5b1a48589694d967096988d02be80b9df3106335d3
SocketDev~socket-patch~OTWPYS.dockerbuild
33.8 KB
sha256:bd8393c67eb9a5107fc0bc4ade404219ad917bc73f73c85192e933cbab545bb0
SocketDev~socket-patch~QITP4O.dockerbuild
18 KB
sha256:4f8336f6bdac6d7ebf170291332adaf865cbc8b015085a23f2d0d3486f25bd37
SocketDev~socket-patch~R7AON8.dockerbuild
32.9 KB
sha256:3e20e0aa4eef5b36d7ebf186490a8773f97ee9f1ea62b2b92eff75ec35ce99d7
SocketDev~socket-patch~RLFVCB.dockerbuild
34.2 KB
sha256:7670ea5eb1095dce416766905c8037eda909b9754a3e4f33d8146573f9444489
SocketDev~socket-patch~VS4BIM.dockerbuild
24 KB
sha256:e720dbbdb937c732048629e0c92e2c97c79566c6b2fd542dd09469e5d171fd58
SocketDev~socket-patch~XSTANH.dockerbuild
32.9 KB
sha256:4f91dde97a774f0efdd7223e9c326aa0dc92004deeac9ac4239e704297a9e28e
SocketDev~socket-patch~YCYW0S.dockerbuild
21.5 KB
sha256:897a22e218b75cf07b4e8ad5e1a4c503bc18faf7aae4abdba56e0428724e9e88
SocketDev~socket-patch~YRFORG.dockerbuild
18.5 KB
sha256:3ba08254dbac8359c0ad808265b717c0f3920f9c5ad5c626dd29fa9c38b8e250
coverage-docker-cargo
27.6 KB
sha256:b390583f94b68452d441b6a1cafa297e6fe7a966ff4ef5bf6afba6e900ef8665
coverage-docker-composer
27.6 KB
sha256:325d71bc46f498b7e70542dd553be117d11522a81e7725762130407dfb4c7232
coverage-docker-gem
27.6 KB
sha256:1b70c7356c0235bc8e0bcb895dc9c24e3aa62ef8faf04d99caf8fc72d66ad625
coverage-docker-golang
27.6 KB
sha256:74ef3ae682d13ebe6981f294ea5687c40ddf94ff68511e14c6536b541f46b043
coverage-docker-npm
27.6 KB
sha256:0c754732776cd0bcf4cf11b6b5e261898392f355c3ac906f0d77d4daee03a20d
coverage-docker-pypi
27.6 KB
sha256:f16bc4ee3c4e402ffc392a596422cc254e9e9b22c5ff8a9b6af39d47ed312954
coverage-host
133 KB
sha256:af260e2b60ba611e44dcac69bc4fa320740f172a3c8a93face8ec27decd0c39e