Skip to content

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

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

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

Triggered via pull request May 23, 2026 14:25
Status Cancelled
Total duration 16m 1s
Artifacts 47

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: e2e
coverage-merge
26s
coverage-merge
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 17 warnings, and 1 notice
test (windows-latest)
Process completed with exit code 1.
test-release
The run was canceled by @mikolalysenko.
test-release
The operation was canceled.
CI
The run was canceled by @mikolalysenko.
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 (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 (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 (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 (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 (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 (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 (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 (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/
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
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-merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, 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~3GT0WM.dockerbuild
32.8 KB
sha256:aff2424665ffb565c63fcd5346d99baa1550e32b2f63ee0f6feed5f99681ee81
SocketDev~socket-patch~4NB3ZX.dockerbuild
33 KB
sha256:05f2526b4c6a88426912b1a45ded6224edafaef4d338e597e60c90655288be65
SocketDev~socket-patch~63834O.dockerbuild
33.8 KB
sha256:9fca538d6fd863929257e9ea514dcae3edfc38e61bfa58c4d61afed9ccf2499c
SocketDev~socket-patch~65RGTQ.dockerbuild
33.4 KB
sha256:5237ab8d32b061f9655d5ad3e1624781410803ae75f298e24501a1507facd8e8
SocketDev~socket-patch~691E9F.dockerbuild
33.6 KB
sha256:a4c5091fb58fcaca67264b6d04d665c27423c2b1ac013b88837257e7368af3a2
SocketDev~socket-patch~946REX.dockerbuild
33.4 KB
sha256:667da67de8a6022ac834e5789aafe54c13b7b8a1999c082f7a9ca7133405abca
SocketDev~socket-patch~BHPI4Y.dockerbuild
32.7 KB
sha256:fd0d63bdde7d1c81623b9dfcf99e69cd62a5f1f31877baaa4945606cbc4fd24e
SocketDev~socket-patch~BV7FCW.dockerbuild
16.7 KB
sha256:2c7bd47bd6c351d34e68737d88cff8ea4f134ecbfb472acb0b63064c0e892bbc
SocketDev~socket-patch~CNA3S1.dockerbuild
33.4 KB
sha256:c82a22303c2c7000f4ff79a46db82d0619e040a4450a9f4fb7b3541d3677787e
SocketDev~socket-patch~D277U5.dockerbuild
16.1 KB
sha256:f2da8ecc42bfb9333d2cbdf71cd8b9c155ce082cdd203236ea0b90578d89fad8
SocketDev~socket-patch~F5VO4Z.dockerbuild
22 KB
sha256:64925711410b6633a49984e089be3f4b988af19dcbc768bae043372e6c7d961e
SocketDev~socket-patch~HZNNPD.dockerbuild
18.5 KB
sha256:09522dbceb75feac0d695db966f856887b5d784b67a56bb7de873a56d8d97a31
SocketDev~socket-patch~JZY9S0.dockerbuild
20.6 KB
sha256:1957dd147d5e6898a1d1cacf2dd0c445ca344639c27c6d508e1922f77fc18958
SocketDev~socket-patch~KBVZ5C.dockerbuild
21.2 KB
sha256:b4e3d536c5537567d6e4f74ee0ede083d5bc1c65e70e8346b05a98a148533eb4
SocketDev~socket-patch~LB8DSN.dockerbuild
33.9 KB
sha256:f9797bac07697efdedee87b5ca362e9c219d7d223a91e04ad2e523e69c6d7d27
SocketDev~socket-patch~LZ6ARX.dockerbuild
33.3 KB
sha256:600e21cf9373c068f84be462d8856a1020419367248701008c525a765757698c
SocketDev~socket-patch~MP8ZCJ.dockerbuild
20.5 KB
sha256:9919bb9145f441973a8bd848f65d489ddc64c507e70eec5b891a7bfffa3a101f
SocketDev~socket-patch~OAZS0U.dockerbuild
33.7 KB
sha256:6905602a0d14b6833375ea1b6895557f613377b79100df56f1110f9888d618dd
SocketDev~socket-patch~OL647L.dockerbuild
16.1 KB
sha256:a53765652c3e97e6ed6accac02b31e32bb5c777bf7c50f525219dbae6d3919ed
SocketDev~socket-patch~R6THJU.dockerbuild
33.8 KB
sha256:07cb92d62cc615b77b618d592b9660824fdaf08a62887f4d1379e922205257b1
SocketDev~socket-patch~SNK2OS.dockerbuild
20.4 KB
sha256:481cdbd4acfbe6a11f2cd80c6f3f772e15fa5ee41b1ca34eb1a9c6ce09371584
SocketDev~socket-patch~SRFNEX.dockerbuild
21.7 KB
sha256:54171adb367f91296ff998451fda3a5fbb31720dadcb2409a70168030d0d6103
SocketDev~socket-patch~T50KQU.dockerbuild
11.1 KB
sha256:6ae50369d967159babc20bb8dea79718362e223f7aeee56bab3248cb7fd5cae9
SocketDev~socket-patch~T8FQUF.dockerbuild
32.7 KB
sha256:80eac7e224b6c1285c88148f88a2629ffa8e32b5e43bd993e3d3dc52048e1834
SocketDev~socket-patch~TZTD0T.dockerbuild
23.4 KB
sha256:8e20c1570e3d95e1762af734066dc4923714f39ca2d414b5e1849308240e5864
SocketDev~socket-patch~U0GZKW.dockerbuild
18.1 KB
sha256:06c1be4e1927f1ffb94b876506935d843619b7b465f89fe714cc8c5416d4318b
SocketDev~socket-patch~UX99V5.dockerbuild
33.8 KB
sha256:e12bfaf21aa4472b549cce0ea6a9e63dcc9042131f0b3ce1da9476ec70128041
SocketDev~socket-patch~VP1JCD.dockerbuild
33.7 KB
sha256:8f910bdb4cf85a0cb39050e59059a4ad9e6d5ad0b425d75822d6dca971ce67e6
SocketDev~socket-patch~W5LWW3.dockerbuild
20.6 KB
sha256:56f2ddfa8f61cefff02f0531e74ad2ef05a0fbbe331f05d4b807aaf42c997bce
SocketDev~socket-patch~WTIO6A.dockerbuild
19.8 KB
sha256:654c65fa3e82835ad2eb22cccc8afe23fc3e015a5dc1ef61617e6293afb116d2
SocketDev~socket-patch~WVPF0K.dockerbuild
16.1 KB
sha256:30ddff5fcc80dd198dff5e556e4589cc610f186f8657da97670f642718af96b1
SocketDev~socket-patch~XDQ354.dockerbuild
34 KB
sha256:a632202a4f5a5110c7f3dc20b1b27ff4f4cbc8e1035bfdc40ee869e534cefdb9
SocketDev~socket-patch~XJ10BE.dockerbuild
24.5 KB
sha256:7a0cdef48347873ae3435f54882af3f441213187b0436744e7fb0b1f78c0a1a6
SocketDev~socket-patch~Y6WJQB.dockerbuild
10.6 KB
sha256:3096a0a9c58f913957db9ea5a7a33f73835ec1577745e07193ae88741e9a0c00
SocketDev~socket-patch~Z89ET2.dockerbuild
33.2 KB
sha256:a510b3fcaf06baad64f9ec57ca0798786725d6f84396e933b8d951d0fe0dcd9d
SocketDev~socket-patch~ZNS3H4.dockerbuild
33.6 KB
sha256:4f01022a1a89687782ce92645624f9c1216e1f9c08efecdbbe5496ae4ead6951
coverage-docker-cargo Expired
29 KB
sha256:b036a7100fe1e35ff09e14a3f8bf5aff245ca5c856c2231d87cef16210bb42c3
coverage-docker-composer Expired
29 KB
sha256:dac4c71ad6d036505c5bcafc835c50e185c4b2538e09892246808abd2d8a12b3
coverage-docker-deno Expired
29 KB
sha256:46526a1efae9e9b2c0ac790480852cc220ef605714293d2aca233575717bee3a
coverage-docker-gem Expired
29 KB
sha256:0b9e43f2132acef7e4a3282e25da266ab6452e8da3e7b899e25dddebce7bc94e
coverage-docker-golang Expired
29 KB
sha256:50a7ab0aef6efbcf04ee93e69ac4ae375dde549a5c8a3400287233edd4311091
coverage-docker-maven Expired
29 KB
sha256:133c3130d5da220fd33f1630e7ff57d347e9049d25e55056ba491a4e5fb0392f
coverage-docker-npm Expired
29 KB
sha256:659d176636b6d1158ae3976e12ed2f825044a021ab17636a920f3c63aa2434dc
coverage-docker-nuget Expired
29 KB
sha256:b208f84a0d85bd48a1596f50ba44ed1798271b3338865302b29ca8c05d975e0e
coverage-docker-pypi Expired
29 KB
sha256:f3e1256b5b6c223763613525afff604978a9385be530749c39ba5d8590c9be6a
coverage-host Expired
172 KB
sha256:cc14ee53dc5ba404dc969eadcea9284d096ce82a9f03676a7f0fc0993bb14d07
coverage-lcov Expired
173 KB
sha256:162eef3013444cda0fa3693e1854d91a392072b55aea90aa8458064e9219ea57