Skip to content

feat(scan): unified auto-update engine — --sync, --prune, --dry-run (v3.0) #137

feat(scan): unified auto-update engine — --sync, --prune, --dry-run (v3.0)

feat(scan): unified auto-update engine — --sync, --prune, --dry-run (v3.0) #137

Triggered via pull request May 22, 2026 08:41
Status Failure
Total duration 9m 19s
Artifacts 33

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, 7 warnings, and 1 notice
coverage-docker (gem)
Process completed with exit code 101.
coverage-docker (nuget)
Process completed with exit code 101.
coverage-docker (composer)
Process completed with exit code 101.
coverage-docker (npm)
Process completed with exit code 101.
coverage-docker (golang)
Process completed with exit code 101.
coverage-docker (maven)
Process completed with exit code 101.
coverage-docker (pypi)
Process completed with exit code 101.
coverage-docker (cargo)
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/
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/
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/
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~022J0J.dockerbuild
34.1 KB
sha256:7a6cb042135974e6f2a1aaccb1408623a0d1e1f6262192f51dd1c18b9fe70266
SocketDev~socket-patch~0P3VA9.dockerbuild
18.9 KB
sha256:ca1e96bc1b290d665a0f7a3f3c9a300855c217f4f51e8526df86660bc95bdc4e
SocketDev~socket-patch~0YINXM.dockerbuild
33.4 KB
sha256:9723a07f8ef98bb3a3bdc030b706ffead1b1d042865e399ca0b520451ba59cf3
SocketDev~socket-patch~4CHODR.dockerbuild
33.8 KB
sha256:43b86e77aec32fab08667e4d62b36e53472c0f788d95dee836e543dfdf0e1db3
SocketDev~socket-patch~54TWKE.dockerbuild
33 KB
sha256:1042e3901dee6321d9ebe4186b4f9f9dc9b1c5a6278360c5e2e26d73ea478362
SocketDev~socket-patch~5TJW3L.dockerbuild
18.5 KB
sha256:b56e360e0103480e2606642f500bf3400ba6ec6b9b4d40ba23af95bb0bd435e5
SocketDev~socket-patch~68KB94.dockerbuild
15.3 KB
sha256:1776eacb79e879000b273a41bc3fb7ae2bb31af9d2b1ddc206b82e5ee8a72589
SocketDev~socket-patch~856LEQ.dockerbuild
33 KB
sha256:76e4da006a1e96c8cb5ab8ea5c502d00d8811671b084771f612dda88bd40a6fa
SocketDev~socket-patch~8PWZ06.dockerbuild
33.3 KB
sha256:9290761e4fda36e37a2e87ad98a7e1e56fcddf726896e50703d7eff44e01478e
SocketDev~socket-patch~9G1LSM.dockerbuild
20.5 KB
sha256:8348e547c8473768504364fdffe2b42333133cdca85795646205773ca8b02dc4
SocketDev~socket-patch~9Q1HR3.dockerbuild
24.1 KB
sha256:fc9cca0852a9b23c31df0e7923dd805f33d2a4bd25a06496dd09e532c2fd884d
SocketDev~socket-patch~KTI2FT.dockerbuild
33.7 KB
sha256:38e9262411329808ec1de6db1ccfc86a11f4867a4883e63ff0c2c1285f0b69c1
SocketDev~socket-patch~KYCZXP.dockerbuild
33.3 KB
sha256:8f532f3ad0238f265538fc6da877cba2d63ab1bd4aba0f8117f439a928f8756e
SocketDev~socket-patch~LEOLAR.dockerbuild
11.4 KB
sha256:69eaca9e5105ab7660e0b1109b8c463aafa36d056c0a38de1f60c85b45be9ecc
SocketDev~socket-patch~MHDFV7.dockerbuild
33.3 KB
sha256:a5ad3876259f1f3d0f0387aacee1cfee1eece7d4be0817539b771fb29880ebfe
SocketDev~socket-patch~MUUQSA.dockerbuild
32.6 KB
sha256:24ea2f1d8717f4b1348301f17f2362c4ffb486d7a5eec779e06f97bc2f404bd6
SocketDev~socket-patch~NM168J.dockerbuild
11 KB
sha256:26c06db682133d0721ea5b8750ce3abe708fb0dcd74a364ed8eee46fcce0ce20
SocketDev~socket-patch~O8309B.dockerbuild
18.6 KB
sha256:3a28d3f930261952c9b11486c0428bda3eebf20eaeace2f733914c01e796c271
SocketDev~socket-patch~OE7QH1.dockerbuild
33.3 KB
sha256:b7f0f12caf74e33996ee9bc3c1942c369776c26ca3ef88ab1a73aef01408f2c1
SocketDev~socket-patch~RA9B1H.dockerbuild
16.9 KB
sha256:12e1a144a248a49e7ac68575c0aa3f033810a80eec0083bcf2acae4b4a8c391d
SocketDev~socket-patch~RQZ4S0.dockerbuild
32.2 KB
sha256:6fd584031b44cd8d9a5dac38ecc37ffb4b2ade67f04d7dd0c75c0652295bf6b7
SocketDev~socket-patch~RSL9PU.dockerbuild
15.5 KB
sha256:7abefd1e3ffd63ced91bbb7289af7cdf44023b4ed88f94ac1e017d4afd8ac8d8
SocketDev~socket-patch~SH2FGI.dockerbuild
33.9 KB
sha256:ee3ea82abd645ff9e8828b207996dd3148e87beb703a77993cfdc63c2105af5d
SocketDev~socket-patch~T50AQO.dockerbuild
33.8 KB
sha256:1aa9f3db76bcb365db15234f14ebff8ed2acb05a24414ffb6a95e609e510fc16
SocketDev~socket-patch~TG9TAZ.dockerbuild
20.2 KB
sha256:ac29f1ea21e3a5afbc49c5514fba58f1d9a96c658482c8cf9b103468e0553e13
SocketDev~socket-patch~TNIJY7.dockerbuild
18.4 KB
sha256:eaffda6005c5a28d6a72166aa0774c5905999450fc23f9011e7ab58190626dbc
SocketDev~socket-patch~V08M06.dockerbuild
33.4 KB
sha256:aae7317b44254d20046289210e0e86589cb7764a686fe5adbafa8cfaee351d94
SocketDev~socket-patch~VZ7MW6.dockerbuild
21.3 KB
sha256:639e8e4673acded7847c22602cef7ff2b4428a3d848ab1c4dc87234f246a6aa0
SocketDev~socket-patch~XOH735.dockerbuild
22.3 KB
sha256:f7401508cd0b7d6d076887cb1a9130b0e892b109735fe593aa78b07f454a0471
SocketDev~socket-patch~XYGT19.dockerbuild
16.1 KB
sha256:a94800d4f2ffe16c016b4a06e1e895efbefdce10d6af2c63fb00c4e390f74c5c
SocketDev~socket-patch~Y42M09.dockerbuild
33.1 KB
sha256:abeb363e8045348335d61c339f46c5ab74c9d68520ddfb314353a1f9c9b79c08
SocketDev~socket-patch~YISMJC.dockerbuild
23.8 KB
sha256:812c8cb3f6d14734faae56b7a844327074df7df00e367ba3e16f3fb867b6170f
coverage-host
109 KB
sha256:36acc33eea841ebdbfb7bf05c8841cd519e1695cc5da0a1be3621a250595d9e9