Skip to content

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

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

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

Triggered via pull request May 23, 2026 12:56
Status Failure
Total duration 18m 43s
Artifacts 45

ci.yml

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

Annotations

4 errors, 16 warnings, and 1 notice
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 (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 (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/
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 (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/
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~0H1TZR.dockerbuild
18.3 KB
sha256:3120ead5fb2b0d90b262d013c10d75bc6c351a7c468ec5099efcac07db2678c4
SocketDev~socket-patch~0UD2QP.dockerbuild
17.5 KB
sha256:ca0f689bcb9081f8aeff53683b11d60079a10dccf98eddd688c28d8e19fe0f7d
SocketDev~socket-patch~0X760M.dockerbuild
32.9 KB
sha256:54c9f9e8a34a980b1f9ca63604dcee6f990a373c4f7f2a05ea3d4f4c31eca4d1
SocketDev~socket-patch~4ZLY8B.dockerbuild
19.6 KB
sha256:19ebbc5fac2f2ace40a916f3c65589846ee59f1ee0f952af9fcb39f4698a740e
SocketDev~socket-patch~5JG3QV.dockerbuild
10.7 KB
sha256:4a77e30ef8f38ff91828fcd6d1ca26ac2e3d52dce3e87f0f629497591ec66d1e
SocketDev~socket-patch~5Q23PO.dockerbuild
19.7 KB
sha256:9fa89758605e76a1783cf8050486c817b9f5ce514ca7d51c272725b909ed0800
SocketDev~socket-patch~8VCYUZ.dockerbuild
34 KB
sha256:92a79e687d3414b7a6d0b4339a705b38f59596feb93a9da952bc271d366c96de
SocketDev~socket-patch~9J2L5V.dockerbuild
34.4 KB
sha256:69bf4af23de3c15092b1c214bd6158fea72786b13f09bb5d9654a5cd3ae853d3
SocketDev~socket-patch~9N3IIX.dockerbuild
33.6 KB
sha256:fae5512d620282016dceb409f6daddee8b34df0342c940863163f83a6c3a35ac
SocketDev~socket-patch~EF8D0C.dockerbuild
18 KB
sha256:e8bb7bb3142d67098322223781808ea6aaa728580de2a581affca00be8f60ddc
SocketDev~socket-patch~FX8CRE.dockerbuild
22.5 KB
sha256:b96757ce3e3dca3a20250328fc35c13de089e03f32999d4d7ca4c194dddf2e39
SocketDev~socket-patch~GBL5K1.dockerbuild
33.5 KB
sha256:23843ad6ab44cc36e124295d1747e2be94704020e8de9f7c1cb1d7686e57b7a7
SocketDev~socket-patch~GW68EI.dockerbuild
33.7 KB
sha256:f0018d124f0821972c72cd41a6e43a5b9ef1961baee6df1954a8b9877bbc334a
SocketDev~socket-patch~HDZIDW.dockerbuild
11.9 KB
sha256:9ad91ea86d73da697d116dc4563c98a86c6963530faf830d11ecc58a1c712d8c
SocketDev~socket-patch~I39GEX.dockerbuild
32.6 KB
sha256:6af9c0c3381a601de009ea50129075e3e2691c40272edb94f82aeb7ccb6e100c
SocketDev~socket-patch~IAT58J.dockerbuild
16.7 KB
sha256:249b12775bcb8a557275f72eb2cb1c45d65199ed08b68cf18cfced904c258472
SocketDev~socket-patch~JLVJXU.dockerbuild
33.4 KB
sha256:1a331786d5f9983365ef99a31445383f62db997967847e4178468851dc2d90b0
SocketDev~socket-patch~K2J3BT.dockerbuild
20.8 KB
sha256:dece45217bc5198dfaf7bade13b79703a5da56ec19a733d5976d2989f87827a8
SocketDev~socket-patch~KM1FWA.dockerbuild
33.1 KB
sha256:6ea83d796931af637b1d42c57033b46eee0f48d734abe554317bff0906ddd6d8
SocketDev~socket-patch~KZ8IZ9.dockerbuild
33.1 KB
sha256:704306ff2ea012ee8826f45b55108f81bd6039b5254d1ffb31ae9c5ea4a481fa
SocketDev~socket-patch~L9CM5U.dockerbuild
23.1 KB
sha256:64175b834cb7a56ee50e7ffcdc0195019914e528c5f2b2d07852a86052add802
SocketDev~socket-patch~MWRZGE.dockerbuild
33.8 KB
sha256:875d971b7d4ad6ad5b85971cd53a8b0ed10241c0ab6dfe0b9fa2ddf04f8eba30
SocketDev~socket-patch~N4J9WT.dockerbuild
32.9 KB
sha256:4fa3f2cdb4a68336f36423abb870a57e57539f3f994697e2eff1ad571e4cec5f
SocketDev~socket-patch~PES90N.dockerbuild
33.1 KB
sha256:204463a4010882267c25f0e03bbac5148b3861bd6d6433d13b055be92be50773
SocketDev~socket-patch~PNXDQE.dockerbuild
24.5 KB
sha256:408e6b5d7c206df0bb7994aef6cf27be9304bcb84d9dc3004f168b67bf66896d
SocketDev~socket-patch~RABI02.dockerbuild
33 KB
sha256:fb27bea966a1baef8ad2ecf1a49491db2b177eb83f32baa8a2778f7ec109e3b7
SocketDev~socket-patch~S0ZL6B.dockerbuild
16 KB
sha256:1d89a8603cd1f9e65cafa7b382221e02e7e12ce8aeab4836eaffe0d7dcea27b8
SocketDev~socket-patch~UKVH48.dockerbuild
20.4 KB
sha256:807408fe695ea37036f2a456f9c471135b7240e002c5178d9f478ae570e3ecb7
SocketDev~socket-patch~UU8VYA.dockerbuild
33.2 KB
sha256:f91e628e06e27e08abd3875e8ce3c7492e7beeed7aa4065ccf4056f1909aea43
SocketDev~socket-patch~XX948X.dockerbuild
21 KB
sha256:18495fc9dda2db8c3c25492a429e2a21883e3f15d5362ef77aa46ecda42cd3dc
SocketDev~socket-patch~YHPGOQ.dockerbuild
19.3 KB
sha256:0ec194c5fd11a116fbd25a12d9efabd5540b527882a6b0b1d2ef37248d6b63da
SocketDev~socket-patch~YV6FZP.dockerbuild
33.5 KB
sha256:f9d5732aabd3d207f5bb4247def36c78138d6bea5f1bae6d2ddce05151129057
SocketDev~socket-patch~ZIP3SW.dockerbuild
34.1 KB
sha256:761a72b61739b1ebbc06ca0bf54a7688a63dc5c55c952ea30edcb06c12af73e6
SocketDev~socket-patch~ZNKLJW.dockerbuild
21.5 KB
sha256:f4d16fac6e5d37f3b3157e9d3bc681eaf5223f0132cd96ccf75ba670421f1021
SocketDev~socket-patch~ZUHBT4.dockerbuild
33.4 KB
sha256:5d75ac7d0058647a6a31d11f1d5151c3bb51e4af8756db37ee23a6995fdf0b1e
SocketDev~socket-patch~ZZFFN1.dockerbuild
16.9 KB
sha256:cc1a9eb2c5b8a5ff5ce62595202d24b7d105ee1ba9602dc6626513a2b8f6d527
coverage-docker-cargo Expired
28.7 KB
sha256:40cfc9473f845849b9690121fde78b3834430bf11275efbb76136ef4a676ed7b
coverage-docker-composer Expired
28.7 KB
sha256:3734073c6ad77296bfcbe55f6a1470cb51a88dc266f297ae24ae0f85d429cb3f
coverage-docker-deno Expired
28.7 KB
sha256:8678028ec11357334b26eed07948d21da01f965512d918eb0a3a9a92cdd6c4cf
coverage-docker-gem Expired
28.7 KB
sha256:ecf53938debd0a3988de68f8522f1b11c6fca2756eec03941028fcebcb6d089d
coverage-docker-golang Expired
28.7 KB
sha256:f4fe452103f7b913cce46b7f6f505b3d7fd16ba439f460e422bcd9e43d48da8b
coverage-docker-maven Expired
28.7 KB
sha256:a69a721d491a4e5f247938964346d7a6c3d71d17c0e577ed2ce7b7f218e0ff6e
coverage-docker-npm Expired
28.7 KB
sha256:10e95a2f37aa04eff22192365ce5f22cb22ba7a79e04ec3ec9a8fe19a32df797
coverage-docker-nuget Expired
28.7 KB
sha256:cfb235a2c3083429bf41261c64ea695acbde9408123f393e7841b731a5fd55d9
coverage-docker-pypi Expired
28.7 KB
sha256:44c45b7b16c6adfdcb7170ae6c50f19ee62b6d8aa65dd5ed3fa6ed4380768f94