Skip to content

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

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

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

Triggered via pull request May 23, 2026 00:31
Status Failure
Total duration 8m 57s
Artifacts 39

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

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 (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/
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-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 (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 (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 (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/
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~0NWB1N.dockerbuild
33.4 KB
sha256:8d9304390dea871ac6891021a778559239d343ff7fb36f3b11985ef136df94d4
SocketDev~socket-patch~1KLP87.dockerbuild
33.4 KB
sha256:b636f3a3f9d368bf2352c57e53e73ecfe0eec990949371d8040a6b11e6e5fcbb
SocketDev~socket-patch~2EXW1A.dockerbuild
20.9 KB
sha256:353339216e20d81431dbe8801830d666bcb27ceb4ac083ab25dd37e50ef8d88d
SocketDev~socket-patch~3U6JRX.dockerbuild
33.5 KB
sha256:24db7026d7f03d35a6bebce05b9851400c296b0d6c849473b87d8cec22764f33
SocketDev~socket-patch~4510TG.dockerbuild
17.5 KB
sha256:f564dcb0735406359a48bd04e4e2261a403909b831e0f8bae0b4f22e87425a26
SocketDev~socket-patch~9GU7ZM.dockerbuild
33.8 KB
sha256:47711c10400326677069695c5af807a4454d07a5c6a0511eb920625855fc50e4
SocketDev~socket-patch~9WGEKE.dockerbuild
19.1 KB
sha256:dbd84b2cfe67af7ea973fe42591ad8007af8f8d5a5ff48c111e93df929f121fc
SocketDev~socket-patch~C0NSJL.dockerbuild
24.1 KB
sha256:fd20e887c4daac79be827e596533878903903b8667e9fc05032e3ee639aae84c
SocketDev~socket-patch~CGTBJA.dockerbuild
15.3 KB
sha256:d7a36266ca30efdc10109c7fba1f59885758f62d0a4bf668e99897438896ff60
SocketDev~socket-patch~F7T50R.dockerbuild
33.8 KB
sha256:81229635463ecd51e3e418c35cd90afa927f706e8b30b98d9f21c7eabce7ab84
SocketDev~socket-patch~GR6SZL.dockerbuild
34.4 KB
sha256:8acd92eb2fee2dca3500bdafff286221ca5f92af4f3ad8e826e3b418c812e177
SocketDev~socket-patch~HC64KG.dockerbuild
20.4 KB
sha256:408a25e7657865ec94a934f2789228758a9dfafe1eaa959960e2c3a349f90a2d
SocketDev~socket-patch~J2FRPQ.dockerbuild
15.7 KB
sha256:b111e379389251e739594e54b70286431f46959fa7a0818e314f591f4c80f3c7
SocketDev~socket-patch~JED084.dockerbuild
33.5 KB
sha256:f1515244cd99a30ea7a0a9f2640a7160a6101176e5b0b5a2e388be2cd960bc45
SocketDev~socket-patch~JXLWPQ.dockerbuild
10.8 KB
sha256:48379f7122307842cf2727e0df4b91fa21fd995bcbc68c436b58ff98e2305dcc
SocketDev~socket-patch~KDFJKX.dockerbuild
17.9 KB
sha256:d9fa04ff3a0dfcdd91670cd62b7c34a4817a33599394dfe236921cd82ab347e0
SocketDev~socket-patch~M1R76I.dockerbuild
34.1 KB
sha256:b7c32a2e2d81e628dfc8655b2dfccec3ef510eb3d4b96f7b786355522a05e22d
SocketDev~socket-patch~M71OU4.dockerbuild
33.6 KB
sha256:3d48fc3b9ac7418efcacecffe36ab808ca6f5f44b37af118f9759e4f4342dd9d
SocketDev~socket-patch~NS5E0V.dockerbuild
33.5 KB
sha256:5c990db82a22a29a84bc29187cb6606472dd3398377b81bd573208ea2d071293
SocketDev~socket-patch~OPGJCL.dockerbuild
33.3 KB
sha256:96301bc86d5713084055c53251bcfbea39b8cb597775130fd8445141c01d0357
SocketDev~socket-patch~P1OIDF.dockerbuild
34.8 KB
sha256:b299ad9128bc9c7d60f43f5e2a5d7dac29de61a279ef5869b430216fa05be16b
SocketDev~socket-patch~PJL5C4.dockerbuild
33.5 KB
sha256:f18adb79574f7eacf9b313de39a72cb8b21c89de21a23f4e6a6068ba699a4416
SocketDev~socket-patch~S760VT.dockerbuild
17.6 KB
sha256:406136fd5fe014e21e63917b1b31258b87870eb1c2f980ed68fd3414e41fcd9d
SocketDev~socket-patch~UNI40N.dockerbuild
11.3 KB
sha256:661d32937376e02e6dd873d32b3e7e515abeb0d80effec06ac22b2b6785e8e92
SocketDev~socket-patch~UZLFBX.dockerbuild
21.9 KB
sha256:1223ac990c3cae46f91126fac71261f827d994489eac493ff792c9645e14f4aa
SocketDev~socket-patch~VKM5FY.dockerbuild
33.6 KB
sha256:bad3d75124be1cf2c2c31fa41b9774de111f6e9187c92d8f41ecb77959a293a0
SocketDev~socket-patch~W2HDIG.dockerbuild
33.4 KB
sha256:80b67d81cbe530ff4194e591f58db3944d303b41b7c1d542a69bedd5dc6f8b38
SocketDev~socket-patch~W41OVG.dockerbuild
16.8 KB
sha256:bec930d2b414f36caba3cf8f2897b8dbf580c64b7688af186cf2c44e78275b75
SocketDev~socket-patch~WH8GXD.dockerbuild
21.5 KB
sha256:18a35c84b0543e25096476901a2143f20d134ecca979da8e49aea7b509b76924
SocketDev~socket-patch~WSUIQH.dockerbuild
23.6 KB
sha256:c968002b102bc584f2d9a73763bcd5960d00827b506156ff68bfe84d5a36529c
SocketDev~socket-patch~XK0NY8.dockerbuild
18.6 KB
sha256:373629f8ffddae61483ad67ff17fce05960b41b6bf4086bbf93515089378f4da
SocketDev~socket-patch~YRH500.dockerbuild
33.5 KB
sha256:eded53ce8d8876acf7f4f72c83439462dd3c872979aea822f84f51eff5f6e1ef
coverage-docker-cargo
27.6 KB
sha256:4beb7b770c1cbedcdc85b10594e39066b518d1431c5d2ebd593cf5f60c87f246
coverage-docker-composer
27.6 KB
sha256:6cb3cf097024ef378be3679deb9f72fca61a0fec6fe1c0aa41026c703ce8f59f
coverage-docker-gem
27.6 KB
sha256:6e53734a015bf41d6933d91b43a3db9ebf4d81b0d5d43ae71b291f31878a1b05
coverage-docker-golang
27.6 KB
sha256:e4e618a8f7513a17849b7d1c0f3d2686832e8721626fede80c7435294f7870da
coverage-docker-npm
27.6 KB
sha256:5e371179fd5848a523ade7cd005271e6efc6ee2edaf9b2dd74027e19e908b927
coverage-docker-pypi
27.6 KB
sha256:f357fa839fbb5782032969440f856c9ff63557caeb5e0ba816184ec8fddb7b5a
coverage-host
132 KB
sha256:29cf777501d3379068019c84fc5081ca8a42036888ed4ee89f97769470800eb8