Skip to content

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

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

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

Triggered via pull request May 23, 2026 00:48
Status Failure
Total duration 11m 58s
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 (maven)
Process completed with exit code 101.
e2e-docker (nuget)
Process completed with exit code 101.
coverage-docker (nuget)
Process completed with exit code 101.
test (windows-latest)
Process completed with exit code 1.
coverage-docker (maven)
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/
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 (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 (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 (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/
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/
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 (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/
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~1DDQXO.dockerbuild
33.3 KB
sha256:e3efdd16180e4a252cf913cf0b573192f54e8d983ca2da7559d7499a46ae4dea
SocketDev~socket-patch~2BHRRX.dockerbuild
33.9 KB
sha256:62c5d53fe0d355955afc3dc94433d3197d9ea6abe21f5b539b4ab9aaaacecf71
SocketDev~socket-patch~2GHUNH.dockerbuild
11.3 KB
sha256:c3b268e9b27c11d66b9a6af501e40f44e86424e921ad976caa6911af28679552
SocketDev~socket-patch~3EZSMM.dockerbuild
15.8 KB
sha256:b0e8c487a81d54d734f8f712251fc70454b3244de430ef97c71c1a7e01ceb53e
SocketDev~socket-patch~B0X8VK.dockerbuild
34.1 KB
sha256:c13eeb50bee4f91b0a817406d99b35279ee2c580417e043fe827990721c0c7af
SocketDev~socket-patch~B2JW9M.dockerbuild
33.5 KB
sha256:d5a3291f345b4425514745af88016d532a44a84937be705af66de51a57c9cb23
SocketDev~socket-patch~C21X67.dockerbuild
18.5 KB
sha256:f6d25aa98f87390d94da4c938c0e463a3789568123104e2a52dedcb96b8c8d35
SocketDev~socket-patch~DP0NRU.dockerbuild
34.8 KB
sha256:f3c4d20b7417cc2142b70455d8abc2f5c4cd9440ae098871fa05ae6c49f3e547
SocketDev~socket-patch~G25AHE.dockerbuild
33.2 KB
sha256:534ddc707fc872a8b63973fd9258db2457de36f1ddbe02f425501fd5055db5cd
SocketDev~socket-patch~HYK9NZ.dockerbuild
19.8 KB
sha256:4f7b7588576f621916fb682c718f0f4aca1fdd26b3914867f5d221d9cde92f0c
SocketDev~socket-patch~HZCG1G.dockerbuild
16 KB
sha256:288a5e5fe582bcbf84abbac8434c59b18f547acc47313a9f66b003413260cf0d
SocketDev~socket-patch~ICXMOR.dockerbuild
34.4 KB
sha256:59dafe818325e0298623f8efe0829548f1313d341aa35a6b5112640790c185bf
SocketDev~socket-patch~IX16MR.dockerbuild
22.3 KB
sha256:f6374f67238b4cde1f87b91b16217d543f92732050900a08594dacd06f59b1cc
SocketDev~socket-patch~JYR498.dockerbuild
16.2 KB
sha256:dd6e637df3c076fa295e3b6df53177b1d4e9369f2e8822761af5f45ec156aa7e
SocketDev~socket-patch~K9IUMJ.dockerbuild
33.5 KB
sha256:dd5557a2fccfd0abac1aede016a092257d9473bff94e5147e60c5fbc8442dd7c
SocketDev~socket-patch~KECVYI.dockerbuild
17.7 KB
sha256:7070bba4193af8ce70624f779fff521d0489a469d00a11dd48f2f6f1ca80ee39
SocketDev~socket-patch~N7RB4Y.dockerbuild
33.1 KB
sha256:2fcd196565c8a277ecf0668f9a5b5ff2521b99976759989bc1a6b951451501f2
SocketDev~socket-patch~NG775L.dockerbuild
33.6 KB
sha256:6dfe25002670f885e3feaa13213846f9f365d98cde08fd0a79b74414b9db43d0
SocketDev~socket-patch~NGLSZC.dockerbuild
24.2 KB
sha256:056f22de8c1bba3ac167a71f127fc2725bb32e8ecfde77f80ee185cb8577d1a1
SocketDev~socket-patch~OZ09O5.dockerbuild
24.5 KB
sha256:6b28e5ecb5e4bcfc014c8028a6b5bae44184704ee7e7e35ae2c921a3fd8faff8
SocketDev~socket-patch~RNOWV4.dockerbuild
33.7 KB
sha256:a71ee88bd8d475233782d777dff9897562582708858dc7868072f07723613630
SocketDev~socket-patch~RX8SJP.dockerbuild
15.1 KB
sha256:be869aad84d6ad94830db487c1deec4df3b83f0823cfd60a3b3fac40cd836a72
SocketDev~socket-patch~SGUNZZ.dockerbuild
32.7 KB
sha256:07a052dc3d0693199d71efa3292c408357d6ca34a2c9d1e9102dfa9cf679275c
SocketDev~socket-patch~SO3QDQ.dockerbuild
34.2 KB
sha256:6d97e2cd4bb7f2707182488e51cedc9c7e30fd1651cb5ba4cd442fb7590fa80c
SocketDev~socket-patch~T46I6Y.dockerbuild
11.8 KB
sha256:8ab67f1d3b7fbce56b9e5c17ad54950c62a545cc93101a48adb2d2fe9c6fac86
SocketDev~socket-patch~T6NQ95.dockerbuild
19.2 KB
sha256:be87e8510d2330ded54b870fbfc9cef0ed882cf6517cf6285d08ee8ab7821df0
SocketDev~socket-patch~TH9HOU.dockerbuild
20.1 KB
sha256:91c0de1cd2c6436cce2cac8a7d555325ab8379755ae5002989192231bfdac53a
SocketDev~socket-patch~TYN43N.dockerbuild
22.4 KB
sha256:3f28bab4a93f5bfbb3e543158b9a597604b5cb86917680868bd0f7105c4786cb
SocketDev~socket-patch~UJKOWE.dockerbuild
35.1 KB
sha256:11f1f9b4a907d1658909d229b96be531c156601cd247183c7aaf17a791e9afd4
SocketDev~socket-patch~V7SUK2.dockerbuild
33.3 KB
sha256:09e5d96484a76a720a61eab2cec55897177e43218d31ea7c24d92cba7555d38e
SocketDev~socket-patch~YGHPGB.dockerbuild
19 KB
sha256:a2750d9e9e2ab75cf664ca94b43d09089649731ffd4543dd80658ce4d99707f3
SocketDev~socket-patch~ZHG1KL.dockerbuild
34.1 KB
sha256:0acaef7707e7702f794a765ab05834915c23017ae070c931c4f854b44dba5ec8
coverage-docker-cargo
27.6 KB
sha256:288ffb8ae2717900d5c7096c69c0b12e98af692d0137e33d6468299033296824
coverage-docker-composer
27.6 KB
sha256:baa84787aaecaa18258a2738f9aa3d2d212b384818b4317b3482b9133062ae2b
coverage-docker-gem
27.6 KB
sha256:94ee008b062f28485b4bdc12b2fd6a44e6aefa708de6af2e25c91e7008207453
coverage-docker-golang
27.6 KB
sha256:5895bd3e99e712294b30b0683980d1989c055c8d982bbbe88bbeb6e77b3075cd
coverage-docker-npm
27.6 KB
sha256:67a82f8f7543342cb4dcf63d1b97832a4e16891e48426330cca30b7cc69dfa96
coverage-docker-pypi
27.6 KB
sha256:a0b3ff7b9b14b6ad40a44c4e61b45ba4b254617728c467db2aa7fd3c3b9e6d42
coverage-host
133 KB
sha256:12d2e0dda74618c2cd47af17ae958fc99f1cd34a8f1cfb19d2ebe51a88e59723