Skip to content

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

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

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

Triggered via pull request May 22, 2026 08:16
Status Failure
Total duration 6m 40s
Artifacts 32

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

21 errors, 7 warnings, and 1 notice
e2e-docker (nuget)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
e2e-docker (pypi)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (gem)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
e2e-docker (maven)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (nuget)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (cargo)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
e2e-docker (gem)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
e2e-docker (npm)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (npm)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
e2e-docker (cargo)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (pypi)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (composer)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
e2e-docker (composer)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
e2e-docker (golang)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (maven)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage-docker (golang)
buildx failed with: ERROR: failed to build: failed to solve: socket-patch-test-base:latest: failed to resolve source metadata for docker.io/library/socket-patch-test-base:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
coverage
Process completed with exit code 101.
test (macos-latest)
Process completed with exit code 101.
test (ubuntu-latest)
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
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/
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~0FPAO9.dockerbuild
10.9 KB
sha256:8b2ef3b1f6870e06bbf40fbfdbf32e909027502e0cd12abcdbe97b722b76f64e
SocketDev~socket-patch~1EKZD2.dockerbuild
10.8 KB
sha256:bbcc5fb3cbd35b94db57f89f8e1cfea701882a7ca31bc2bf402962a2f79af076
SocketDev~socket-patch~2VJ7Z5.dockerbuild
31.8 KB
sha256:b665fd22868b19f2f5fb25c5bca3d9f02f3c851493719fb978f0357b51d728d9
SocketDev~socket-patch~47UPZG.dockerbuild
11.9 KB
sha256:3502c406d8684b32cd7b9a7aa64bd4a08baa3fd56012bc1338e1f968162b7011
SocketDev~socket-patch~4BTQ9P.dockerbuild
34.4 KB
sha256:f734be1ddd5827e4a83d8c326a0fbd068832309b4581769b044eb8df35ee69e2
SocketDev~socket-patch~4II9I9.dockerbuild
11.6 KB
sha256:0e9325d19d0c932049a45d6a0654ba108b915781777e250a5919db6706781572
SocketDev~socket-patch~6JQ3RD.dockerbuild
12 KB
sha256:3a3854d52d813707bbf01a038777165f2c068636510857b618576d92e1aa804e
SocketDev~socket-patch~7HWJ43.dockerbuild
33.6 KB
sha256:7f6b388297389e18e18b8993567d7ee0ea0ae176780bb2d044d3fddade961bf2
SocketDev~socket-patch~7OUCO5.dockerbuild
31.5 KB
sha256:c3f2b43d95f9c1ef9ddeda8021b7947bdd4fb517e2400c0d7e5da9d3b94ffa71
SocketDev~socket-patch~93FFPB.dockerbuild
31.9 KB
sha256:cb0fd1dc2f6bc9b2c10b1d945b129926628ae0d96fc91a54bcf15232ff53e290
SocketDev~socket-patch~E9YSBN.dockerbuild
10.9 KB
sha256:403872c1be7279f801cbf3ea2608c3996f70b17b85815c4433ed676a55d44a9d
SocketDev~socket-patch~JLRGMC.dockerbuild
11.1 KB
sha256:84f77f480a8c48e28bf8bf1a4f15859eb83214e4828550910a7a4f9d5440c587
SocketDev~socket-patch~LTPPRB.dockerbuild
11.9 KB
sha256:c833f266fcd818d430a6a4adb162cd493ec4b5e64dfbeb56bf1fc70595dfaadc
SocketDev~socket-patch~M3HIFM.dockerbuild
32.6 KB
sha256:ffb1bc9679848ced6069de78fb5a7796b140ed53c6f046f5d451994450c83ab4
SocketDev~socket-patch~ME0OQ7.dockerbuild
11.2 KB
sha256:9e1f36eb9d93d8428aab57c7fd92878fad81b295b412bbde19413d7f33b2e50f
SocketDev~socket-patch~N8H6RQ.dockerbuild
31.7 KB
sha256:0fa235af6e9b6d49244f73c51c34d89f7b44ee03a749546262d934b9a7f4833d
SocketDev~socket-patch~O2ETE4.dockerbuild
31.7 KB
sha256:dba8fb7ee267c3a61af2dafaac03e9f8738d72ff790461592a43f9aad86d0e69
SocketDev~socket-patch~PEHHVI.dockerbuild
10.8 KB
sha256:25735c3436b4081db4ec46b84133f7261c0b95d12bdf6fa0e285fa730b04f322
SocketDev~socket-patch~PFL2F0.dockerbuild
12.2 KB
sha256:0a60140ecee624df55b6c9961ea0a8242a36052c12b918eb9b63fa8fa265d35f
SocketDev~socket-patch~PPT10U.dockerbuild
11.3 KB
sha256:4af018e451e9041876702219b5bfd4f43cc7e4d35b6cb2c01d002ff989d984b9
SocketDev~socket-patch~PTBZTS.dockerbuild
12 KB
sha256:2f52524d759dfcb25607fe80d038133514127fc376bdbbbb0f9b037c98edf049
SocketDev~socket-patch~QM8E08.dockerbuild
12.2 KB
sha256:3a74993f41f5b26da8dc8ad6becb6543d5929eef3f67f10bc4fc6ec9240092c8
SocketDev~socket-patch~QXQSJ7.dockerbuild
11.4 KB
sha256:120d1b243a60cdc8bfc13611f7bd6c44ac04db2cf522dfa01390fa1b45327906
SocketDev~socket-patch~RQ4EUY.dockerbuild
10.8 KB
sha256:c5527ce7a44f48f0d7a168627cefd36fca372aa79eb3cba96769f058942a3963
SocketDev~socket-patch~RVBILU.dockerbuild
32.6 KB
sha256:5b51d6d4946980dde51222c1ccdf9c7072338c7814c139e36ea7ef7d3e97405b
SocketDev~socket-patch~SW3DFP.dockerbuild
32.4 KB
sha256:8af0d8904e2d3b879f22bba72a8b96df767ead8c7872b0f7f114c07d3fd18b25
SocketDev~socket-patch~TM6T7T.dockerbuild
32 KB
sha256:b0d41b406a2befe2a56ca315cea007b597afadeafb9cd717aad69d631d685e71
SocketDev~socket-patch~VPXDPR.dockerbuild
32 KB
sha256:8ed2c053d263e314673354bac7c74196c1dc939fe1ef5c264c17eb3ee4db756c
SocketDev~socket-patch~WNXDUQ.dockerbuild
31.4 KB
sha256:ee8a91e6b92ad661c8f79ff46a5b724a9f268fe6e66286e95ca6c7808b5efd42
SocketDev~socket-patch~X62OKN.dockerbuild
31.9 KB
sha256:d51e1a82ccfb3cb3a44c03cb68928c3aca76cca34cbc689884d01848ce5c1b49
SocketDev~socket-patch~YXPWEO.dockerbuild
34 KB
sha256:32ea45197f0c0b2047a680e3f6fa20d67ea56e1cfa64c3b1bb1df9651e27482e
SocketDev~socket-patch~ZOTNPS.dockerbuild
32.1 KB
sha256:e30bb288847a4bf50902ef0e54ab0b7d9fce33752ba8f18e5f3250489d1056fc