Skip to content

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

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

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

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

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

8 errors, 16 warnings, and 1 notice
coverage-docker (golang)
the remote end hung up unexpectedly
coverage-docker (golang)
could not read Username for 'https://github.com': terminal prompts disabled
test (ubuntu-latest)
Process completed with exit code 101.
coverage
Process completed with exit code 101.
test (macos-latest)
Process completed with exit code 101.
test (macos-latest)
could not read Username for 'https://github.com': terminal prompts disabled
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 (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 (nuget)
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 (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 (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/
coverage-docker (maven)
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 (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/
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 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~05TUV3.dockerbuild
21.2 KB
sha256:73bd8db2be462638b4800242ca346cc614bdbfaa7644c8aeba2746cde097f9dc
SocketDev~socket-patch~0K9UC4.dockerbuild
20.2 KB
sha256:158125607837d61a239e93a2c372729b83074f76e899f495b9faa8c678fcad86
SocketDev~socket-patch~1U1H95.dockerbuild
11.9 KB
sha256:f9752d51da4f667daa595d213acfc34de22c18b9e9056312d8bdac01f8c2a2c3
SocketDev~socket-patch~3GCH2P.dockerbuild
20.5 KB
sha256:eed9b7bc70307c633c91b5cc80f1b0a2457c801b54c8c77ddb60ea034c83d867
SocketDev~socket-patch~501W65.dockerbuild
32.1 KB
sha256:3e4b961e846520d2b8b225c07da7e4b4976fc8a31ef5e2b623b0fbecf26dfb17
SocketDev~socket-patch~67VZ2N.dockerbuild
34 KB
sha256:be907a1de0acbb3f4493671ee9242b18043d7f77cfec8b431d0d7ce04a9589c9
SocketDev~socket-patch~6CJB8Y.dockerbuild
16.4 KB
sha256:c15bfc2be8a11fbd627d2b879269597cfc9fd199e328e92d0cd20de2a815492a
SocketDev~socket-patch~7OVHK0.dockerbuild
33.7 KB
sha256:d13794a0f0e60f74f1902f1b4818602726a8e5152855e2611311541866b0a84f
SocketDev~socket-patch~7WDNSP.dockerbuild
34 KB
sha256:19e6ffb9859e72884e583127bd671d88d01761bee0c116f0c07e78dc9767a8d2
SocketDev~socket-patch~8FMKQH.dockerbuild
19.7 KB
sha256:3849ee61af449b473dd6045cd5b5aca6cf739c35f5ea8cfd46983c8260146e26
SocketDev~socket-patch~8YRMNW.dockerbuild
17.5 KB
sha256:c723d04702530648281994965360f4e6d39ecf4819353fa40664f3e079bc3346
SocketDev~socket-patch~9BFD52.dockerbuild
24.6 KB
sha256:8482725c565e682604dd117f2a5f30d2a309e150872f435cd3348cbb7110a920
SocketDev~socket-patch~C7SX91.dockerbuild
18.5 KB
sha256:89eea0fae542547798fdb92b77835c596f1227f93be6af2e464745dfde25259f
SocketDev~socket-patch~CVM3H4.dockerbuild
22 KB
sha256:7ba3903909fc1c444b1b08ee56e066f1dabcd5d65f8da39926d85363230058cb
SocketDev~socket-patch~F5136E.dockerbuild
32.9 KB
sha256:3709b3751fc95428c2efa515e3145cd954615a0ae0ed520b63482d4a867a2b18
SocketDev~socket-patch~HKV643.dockerbuild
33 KB
sha256:8628abb7533b59afbd0d00949251f77818ad9d2bbc3819e280382a21e46d1eb8
SocketDev~socket-patch~IVUGAB.dockerbuild
10.7 KB
sha256:f7ff16c7ed5cd4ef0a2011e05d27e13bc8b8a470f02778468f0bd9a97d73a1b1
SocketDev~socket-patch~L0OOVS.dockerbuild
33.7 KB
sha256:1a96c5e493f5f2c4d2aee40c41e1dd335b36f9ed858838bf022abc745f150c81
SocketDev~socket-patch~M63X5W.dockerbuild
33.4 KB
sha256:d42f15b36d0bba00e927942f5876d21c178869bebb8aa1f9bd5dd145c8c66bdc
SocketDev~socket-patch~OCYDC5.dockerbuild
32.8 KB
sha256:eb0a222df489018748171de94db832b0627499d88de0694aa88d426770654a11
SocketDev~socket-patch~P1EUBP.dockerbuild
33.4 KB
sha256:652095af0bc4a36c87664ea2018a15e457dd20c206f27ed09a6d671ae5c1df61
SocketDev~socket-patch~PRGMBO.dockerbuild
20.1 KB
sha256:ac4827261dbd629ba01693a23c2aeeab6febbdc67e79efaa86b5e06f2c1550ad
SocketDev~socket-patch~QP4H7D.dockerbuild
23.8 KB
sha256:980aee261b25e600c3beeccf06bdb662312752bca49355787526919c488b9e69
SocketDev~socket-patch~RUPWRD.dockerbuild
34 KB
sha256:f773e408f89610a9bb64a04e82286e9b28e0825a230ac8a3d5047a209be3acac
SocketDev~socket-patch~S3DR4T.dockerbuild
33.5 KB
sha256:46822209d132d6ec497d90ba50cc02aa3d1a2cd6224fce03dc9ec5e5c25ed0c6
SocketDev~socket-patch~S5HGPF.dockerbuild
33.9 KB
sha256:ade873700baef3d4cf6875cdada8d9a3d62a2fc0a77a35428c5edf9d8d0e3085
SocketDev~socket-patch~SAFMAQ.dockerbuild
33.7 KB
sha256:ed9cd9f97646408ae96b9e41afcb87f9bd89b18d6bcfd1c8ddc22b8c596ad505
SocketDev~socket-patch~T33J4N.dockerbuild
17.5 KB
sha256:dcb6ca86c1abad9ec0387ff9cbdbe860a59fc51d15c4202268b3de0e9ec67fae
SocketDev~socket-patch~T6DWKO.dockerbuild
16.1 KB
sha256:4b6e124cad41398f164313aacd5b96d3eec38d1f0502247f375f56abaaaf33a1
SocketDev~socket-patch~TNKGG9.dockerbuild
33.9 KB
sha256:b26f47bd09f9b21f2db3f0ca302f99a3dd0dd330f0cb2ec10eb759b48f15c7c9
SocketDev~socket-patch~WS75HN.dockerbuild
32.6 KB
sha256:5e677d142e17350d0645b9ca79ec9c337060634045e9c63fa7efd749275d260a
SocketDev~socket-patch~X86Z5C.dockerbuild
18 KB
sha256:b1c04501b343625a903b4c2d300aa49de3b2ac194f43ff273f5ee4f90d3bef33
SocketDev~socket-patch~XWLWBY.dockerbuild
33.5 KB
sha256:2e8aa412c7eb42ea23627948386cda353404e1a5877ce13a108e4947813f369e
SocketDev~socket-patch~YO8K2C.dockerbuild
33 KB
sha256:f998fa32e0734bc457eaa1edcbc83c0a48ddbb4502703e07fabeaf6f1cc19c8d
SocketDev~socket-patch~Z2SL1I.dockerbuild
19.4 KB
sha256:308c8532cd33c628bd637a740fac7c23566075fdfa7ed5e754d48de5d7a6c1b5
SocketDev~socket-patch~Z9HYU9.dockerbuild
20.8 KB
sha256:c1a65e7b56ba5acd3916ca997bd623c325bc7e8edf9a3b2e476fbb9ff3364db5
coverage-docker-cargo Expired
28.7 KB
sha256:a1caaac4ab5a1075d9235e397e97498f710b2e67d772418d7e1257a457f654e7
coverage-docker-composer Expired
28.7 KB
sha256:3cdaee813154c8e06207af781761b6f7d4b9c2e95ad752666becbfd9bbe5efb3
coverage-docker-deno Expired
28.7 KB
sha256:97ccc2d2d886c66e633f5283ab5335a2dad3e5474a95d423af6ef1bee58fb692
coverage-docker-gem Expired
28.7 KB
sha256:02ec42353622fb4188173a3ae19d0315f5755cd0574ff887697017c136ff4fe0
coverage-docker-golang Expired
28.7 KB
sha256:bfb6e76d6a54225bdbfdf16f0122dd0586fae4a5abb63bb0f540bf2bbdeddd6f
coverage-docker-maven Expired
28.7 KB
sha256:271d071913d70f5144eeb1738b3d4a6f473842a8577c3918d9073de0877dd02d
coverage-docker-npm Expired
28.7 KB
sha256:bf0635eab3ba3127e2716b1335f71dc2a6aed6c7af8ab3997463ef8fb224f853
coverage-docker-nuget Expired
28.7 KB
sha256:bfd1d532f464dbcae5b480cfb03d12fa766f0b31fe0e9ef1cb89f908fd84977b
coverage-docker-pypi Expired
28.7 KB
sha256:f623da68e32aabb5d419a5c9a72cd6f7a868b80abed3432596e68fa9606b06cb