Skip to content

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

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

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

Triggered via pull request May 23, 2026 03:19
Status Failure
Total duration 12m 48s
Artifacts 38

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

9 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 (ubuntu-latest)
Process completed with exit code 101.
coverage
Process completed with exit code 101.
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 (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/
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 (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 (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 (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 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~2664IC.dockerbuild
15.1 KB
sha256:386edc39461fa4957003e6d1feeff5bd737359ca49ab5060cfbaf340294be4e8
SocketDev~socket-patch~3ARDTK.dockerbuild
34.1 KB
sha256:99e60ca55e12978834e296192de534e0e1270d280a2900d5c70cb22a688e48fb
SocketDev~socket-patch~3TA1YM.dockerbuild
33.7 KB
sha256:285c3e1ba1938f09ddca7d97e4df0cd656be88692af856937c0748b68af466cb
SocketDev~socket-patch~490O6R.dockerbuild
33.8 KB
sha256:b3256e50e60215343444c5e2ca7bcb2301b81c3f313a1eabdb1b8a8ca3516162
SocketDev~socket-patch~6X73Y7.dockerbuild
33.9 KB
sha256:c49f2d66fb1aacf4dac1953f00b065c41e90fba1bf72c0e7a87900484d900e8d
SocketDev~socket-patch~77WKRI.dockerbuild
33.6 KB
sha256:b0e4fee2a2285f438594b4f94479ae98487f5bbf8485af20ec5294f073b2d986
SocketDev~socket-patch~936UAK.dockerbuild
33.3 KB
sha256:c52575c5b2fb370043145ac1bca653de25ea913121cb07012c7ac31c40eb5ed5
SocketDev~socket-patch~BK5GSG.dockerbuild
33.9 KB
sha256:bb7c93e3b03df8e91030f0c3d6c5bb6fc9e041814f236e659c533215506b9432
SocketDev~socket-patch~FQ3JM7.dockerbuild
33.8 KB
sha256:4e84bb15112d35756a68734453e77fc06bf92fc41ca7cb666b1275ae166cad9f
SocketDev~socket-patch~GLWI5C.dockerbuild
15.7 KB
sha256:bd3cf63a6be4c6d7cf56951f1f4401d2d51e72e0df4c96ee6e258d0addf2e361
SocketDev~socket-patch~IEG8WP.dockerbuild
34 KB
sha256:f75988c800855753d67100e9ec8d30b55818b2e06d713e2a92e180b88a594b1f
SocketDev~socket-patch~IMQU02.dockerbuild
34.1 KB
sha256:7643aa6fe4729103acbf613cfd897acb400da006ed15ef1d50be3a665a1503f1
SocketDev~socket-patch~JD8RBG.dockerbuild
32.7 KB
sha256:bb6ddf01685691d3b00a8ddc4751f07fa25edb8bda1c03c8da6c6ab33d6aad25
SocketDev~socket-patch~JTZZHI.dockerbuild
18.2 KB
sha256:ea655eb224343eea910146cf12f3240360e5f9110537aaf49dbd60352dfe28a9
SocketDev~socket-patch~JUTWJJ.dockerbuild
11.1 KB
sha256:857f0135e249ad06de84b90bba629aa7334dd3faeedbeb996ae38c616092a55c
SocketDev~socket-patch~L6MCZ3.dockerbuild
11.5 KB
sha256:e75253ae014592bd3e3f702a307cc6421a7611dbc7b629fd45f39631679c8eac
SocketDev~socket-patch~L8AMN2.dockerbuild
33.5 KB
sha256:78be7aad71cb9d0a414e9b3afcc987581c49893e37add1512ef08ffb7850c1f7
SocketDev~socket-patch~LS4RW2.dockerbuild
33.2 KB
sha256:95e12f38bd4db1dbde1d3f48d9fac0a84ce88fa6ad915b77384ed3ac428e1cee
SocketDev~socket-patch~N8AZNI.dockerbuild
17.5 KB
sha256:5a9e6c1a7ea1142910aecc8d81841030fd679d50d1a23cba5f704a9709edc5e1
SocketDev~socket-patch~O1XCFR.dockerbuild
21.5 KB
sha256:d01eea52cb97b6479e0b07e36f0b6c50a16c1fcb9755cfb522be24c18f230bb8
SocketDev~socket-patch~ON7QIT.dockerbuild
16.4 KB
sha256:7d3ba8e71ad7c42a62412abb69d35ddd3e22b6fb6cfc7e34a8b0c6e3d8938ea1
SocketDev~socket-patch~P47146.dockerbuild
34.1 KB
sha256:5f4972cbbc50769cc963fe643478b0979bab729be0357bba91a6fc7b4078c9c8
SocketDev~socket-patch~P5FEKF.dockerbuild
20.5 KB
sha256:8d44c9630afb5ea377afef79a0d7061ee41715e5b774cd5e1552043ae90cd6dd
SocketDev~socket-patch~Q1PITB.dockerbuild
18.7 KB
sha256:ff78fa9a50bfb06a7da8fd5a6010d9e23dd3f1a7aa2de0a311a244c8f19b6f69
SocketDev~socket-patch~RQP74P.dockerbuild
21.9 KB
sha256:a1c26abfaa6b80c91030b63ea4d6e7dbc51dc7af54e6b5310144e7c156c047cb
SocketDev~socket-patch~SBZY7D.dockerbuild
25.1 KB
sha256:0d9cb234890e6fc9540bd15e5c35adf5147e5771fe6a39e0da694a0eb2089cf7
SocketDev~socket-patch~V16XFZ.dockerbuild
34.1 KB
sha256:f84ad6b97be581f3fbfec542faed3a2bea0bdc6ca1785d2e44f4de8b8796cbab
SocketDev~socket-patch~VZ7ZON.dockerbuild
24.4 KB
sha256:bf9ebf647ed74283dff991321c4c3993b28d8bf9000c5f7d39cc25a391072f29
SocketDev~socket-patch~XKDJZ5.dockerbuild
19.8 KB
sha256:e8b1fbfc9382ccd18dd8d5d3f1fb1c1765e8ee8022680967657ef42596abe5c8
SocketDev~socket-patch~Y4SF85.dockerbuild
18.3 KB
sha256:1896f6ddf869ffaf77df89411751c66dcf15306c82634d6ecafb8d625374ecb8
SocketDev~socket-patch~Z083J5.dockerbuild
15.9 KB
sha256:581f45b729ab197b5e35cac14b2e6211db5803bc706bb6b5e98fa49d3396cd29
SocketDev~socket-patch~ZRKYXN.dockerbuild
33.4 KB
sha256:b849445e646adf67877616c8deba5eefe2b24a077f70af9930bf649d38e196a6
coverage-docker-cargo
27.6 KB
sha256:0057dc541eb1858070d08685bfab994b5ff9ac86db3f2a1bed4c027679b71a07
coverage-docker-composer
27.6 KB
sha256:cdc12ecc8ab8ebc08f072344ef22eca151e2dddcdc401da4b93a963e63367d38
coverage-docker-gem
27.6 KB
sha256:f7a63ae347abb46d5a7e3deeef58d3c8d5411676dd98d9512ba8e275758ca668
coverage-docker-golang
27.6 KB
sha256:4d2d3502e19bad09c7a05e792b11da8908216dd04d6502e5c265c81a8443a970
coverage-docker-npm
27.6 KB
sha256:0bc7b086bd3e3872f934fcfe3db6cecc00209e5b57a46099094d0b806d69edec
coverage-docker-pypi
27.6 KB
sha256:97f13fc7f8d89709d4f347bf0062dcc34307453241bf1e73f908b7a3efdd3785