Skip to content

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

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

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

Triggered via pull request May 23, 2026 00:35
Status Failure
Total duration 9m 10s
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 (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 (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 (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 (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 (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~27KGII.dockerbuild
18.4 KB
sha256:f01306940b5907693c695db45907181170938b96d750ec18ae31685de7a79e63
SocketDev~socket-patch~37QCNQ.dockerbuild
33.3 KB
sha256:43622eb2432f4215c1eaed181b411082855728487b96eecc3021dcc2f8917e00
SocketDev~socket-patch~3T1IWI.dockerbuild
34 KB
sha256:225cb34938bc66fd5f06560595aa5e2256e9ff18bfb896c2154cc94dc068aead
SocketDev~socket-patch~3WPU2Y.dockerbuild
21.5 KB
sha256:5c7cedfe9c078132e20d43900b0fc2030c09379d9819231972aeec29dea8f107
SocketDev~socket-patch~4FM3U8.dockerbuild
33.2 KB
sha256:7d33d599124cf1c3974d38102f5af9e84d701e105b99ac25772bb83d91c1295a
SocketDev~socket-patch~8F269C.dockerbuild
17.5 KB
sha256:7f9aea59d6717078c37951777f6f05f02f05c6c2283450d41de92b259bc99005
SocketDev~socket-patch~99BXW5.dockerbuild
16.2 KB
sha256:2e59581d964c200f9afd642659bad81122c20eb71aa2bc16b4194dff7fd123e4
SocketDev~socket-patch~C8Q16A.dockerbuild
33.2 KB
sha256:6fc367d7fab29be3dc1a61ef0ceff2477ee415dcc35b303ee564eb8b0146bb9a
SocketDev~socket-patch~DY5RDI.dockerbuild
33 KB
sha256:5f0c3fe8562bdff444b3e70251c2665dbbee7ee5aec9e75ae1053a5aa696d90d
SocketDev~socket-patch~DYX8TC.dockerbuild
18 KB
sha256:5ba6e27c6f95166184ecffb57ed16e05c4689ace3038085be1d5a54a2a48db2b
SocketDev~socket-patch~EZW9MY.dockerbuild
34.4 KB
sha256:7b0324fa2ac613a57dfeb01bb0ffbd9101af8f3256840c427527c0f8b5c83ecc
SocketDev~socket-patch~HYGPE6.dockerbuild
32.9 KB
sha256:6e8d415d71600df68efec90579f48c692f58be3041bd933d818c31f5ce24d440
SocketDev~socket-patch~IHL9LE.dockerbuild
17.5 KB
sha256:8aea593d7835e8d8b121315feec93cf7726a86365308538f168c07adedd8e673
SocketDev~socket-patch~ISDYD1.dockerbuild
33.7 KB
sha256:ac9896820242b7b7dbd03899b5c29cefc7be2c9d4a04f3069f07b4c7f478af38
SocketDev~socket-patch~J93SCS.dockerbuild
18.3 KB
sha256:c8e81428324c69cb0e3a8ee62947ad04994b774aee8d437c11fe68e8abb10281
SocketDev~socket-patch~KKJRK3.dockerbuild
34.3 KB
sha256:c40932fed923017efd0b27c10880bcdb47c7f0b59d24559b1c30b85ecc9c87af
SocketDev~socket-patch~NZ6BB2.dockerbuild
24.2 KB
sha256:37a1694daf3e5a0bd93e947e96fb9d42d5fd5f52c12952c82085e49ab5564f34
SocketDev~socket-patch~NZTHPK.dockerbuild
20.5 KB
sha256:720a4096a60fcff3be62f4542c3d3c1818e2f8819424320118822fd562e852e9
SocketDev~socket-patch~ONVG55.dockerbuild
20.3 KB
sha256:11dd83eb0c8dbe6ef862bcfc56d50eb686f8b55d62f609a04962f0f66ac9e138
SocketDev~socket-patch~PM7VVB.dockerbuild
33.5 KB
sha256:1a92fbb0e14eec16942c418a5460cee75a2c74a29df4837187d677996954e4a2
SocketDev~socket-patch~Q10O7E.dockerbuild
11.5 KB
sha256:e72751cdd6c120a26a4e58724a2f5653ac48c834b30512ec6fd69ba50fdb05a0
SocketDev~socket-patch~RA6ZM0.dockerbuild
33.7 KB
sha256:a2b546c34159c8df955ccb422ac70f6efa1cdc3ba72c07eab84c6aa5cece4a34
SocketDev~socket-patch~S0MSCH.dockerbuild
33.4 KB
sha256:1f9eb388def7452f1b071cc4f8258847a4608d1efdcf13f63aa8ffd5f1453708
SocketDev~socket-patch~SJ8HHH.dockerbuild
15.6 KB
sha256:81d0dfbe4e1eafe673ef3fa72dad269e371748fdf8cf698a8fbd20317fa51dbd
SocketDev~socket-patch~TRPAZ3.dockerbuild
24 KB
sha256:58a83347e1db300e6d5c169449091afda390f97d911c87aec7813bcf8800e5f7
SocketDev~socket-patch~UDHE18.dockerbuild
34.6 KB
sha256:e5e13a112d1a1189e66e489525e5cdd82210e2d795156f19640118754751214f
SocketDev~socket-patch~VI4SU5.dockerbuild
11 KB
sha256:30b6ff7074234433a826a7b5c5c9713c9e3bf3b4e489f18020c75d5ac89675f2
SocketDev~socket-patch~W8P4QU.dockerbuild
33.6 KB
sha256:3623b880b1b1f566141f493d13e2880f1dfa7620d72a8a6c19c19f092cb6525f
SocketDev~socket-patch~YB3R81.dockerbuild
33.7 KB
sha256:111b269a604aa3473d405579253f5c65c31b66be66e031c5834994f271f72990
SocketDev~socket-patch~Z7BQQH.dockerbuild
33.5 KB
sha256:b3dbd6bfcdd4b2403ca24b409ac80446351750ecee4bd93ec14d454559d0a18c
SocketDev~socket-patch~ZDA35A.dockerbuild
21.9 KB
sha256:1a95a0ab8f84ada6188f0cad73352cf0ee9f467015f364a53b38c5ecda871c78
SocketDev~socket-patch~ZMR1OJ.dockerbuild
18.7 KB
sha256:6cec76108b92429041523dd58fcf1650136e6dd1e4d5038426f2e324ba81d70a
coverage-docker-cargo
27.6 KB
sha256:d5cb2a2b4c0f0e2334ccdc3d33837b5dcb0d2006460126ca1981bc68e89a576b
coverage-docker-composer
27.6 KB
sha256:2b295190e3f5accb91ba2170eb444220bf4e9a917efebaff684178c956c98d6e
coverage-docker-gem
27.6 KB
sha256:fb12530cc0e905f896001a9bc417ab31366901627dca3b616f3c03cd72efb58e
coverage-docker-golang
27.6 KB
sha256:605fc0cc389928d171cd61f517b1fe3907f822506ed80987f780bac9af6bb0cf
coverage-docker-npm
27.6 KB
sha256:ff4212d5ee12816830dffb625141b6173d4058f5bc8cf325d8f38f5e55f6939a
coverage-docker-pypi
27.6 KB
sha256:109804fe24fef40b6186e4d46b0b6ee7307eb9431e3ac9d21712da06b58a205a
coverage-host
133 KB
sha256:6b54bf4f4ff9eae44224cbb9237d730f232c7b41d9b368678bd6aaafdb787ebb