Skip to content

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

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

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

Triggered via pull request May 21, 2026 23:23
Status Failure
Total duration 7m 55s
Artifacts 33

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

20 errors, 7 warnings, and 1 notice
test (ubuntu-latest)
Process completed with exit code 101.
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 (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 (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 (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
test (macos-latest)
Process completed with exit code 101.
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
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
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 (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 (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
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 (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
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 (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 (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 (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
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/
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/
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~4K74TY.dockerbuild
56.7 KB
sha256:5c4ac7be660fa9dd670bfb1ce7a311df1ed8bedec70dae374aa95cf2be83c7c4
SocketDev~socket-patch~4RU2BK.dockerbuild
55.5 KB
sha256:fa46376cc6c92952b3c67347d7820bf07104e27ee6d54571497253fd144790e8
SocketDev~socket-patch~6UVE3B.dockerbuild
12.8 KB
sha256:a2e6d3d2f8e843642a9fef795bd97a29611d8394944f7847a707c124aa7a5f8a
SocketDev~socket-patch~981QYZ.dockerbuild
11.3 KB
sha256:422c8301db00ba74b428544a44d68c37585753f2dfdc32a5edbf5551144becb1
SocketDev~socket-patch~A2LX3I.dockerbuild
56.7 KB
sha256:18b531f2e671f4965048cc103f056cac892524cd56767cc3b403d836679ce62e
SocketDev~socket-patch~BK8RXW.dockerbuild
56.7 KB
sha256:9fd0c1dddfb9df842586f09c6f02d52b36f5d27618bb607d7e55db541fcfe204
SocketDev~socket-patch~DFI99P.dockerbuild
12.3 KB
sha256:e997fc0fefef1e66281dafd618bf6000eeef208d7bf21561b9d82cd11430d58b
SocketDev~socket-patch~EFAGYC.dockerbuild
56.6 KB
sha256:f768f9765012d8ea31788a7d8280ff741d87461421c7836bdbeb73aa7fbac953
SocketDev~socket-patch~FZ2804.dockerbuild
11.4 KB
sha256:79d971fce52ad52c186c5777b3e4293179421b7e07fefc1d12f83de1cae68b32
SocketDev~socket-patch~H27VS8.dockerbuild
56.3 KB
sha256:cc98dad0ff2dfd48af79d50c187b888e3491f01ab3d9046e5f252a59256cc76f
SocketDev~socket-patch~HIDJH7.dockerbuild
56.6 KB
sha256:910a2c14c245c81d5bcd31d657618c2362fd21eade547e7569d917bbb4d68c0a
SocketDev~socket-patch~JXNGOX.dockerbuild
11.1 KB
sha256:cab7230d979ec8d67d3f0c9c6e84bb3f21ea5f8bbbbbeafb41b156528afb0e95
SocketDev~socket-patch~KRBEZM.dockerbuild
55.5 KB
sha256:800c61b0ccd24a02387a3cb283d848e5da6a60abcf70d29d29d864b969fc4ea7
SocketDev~socket-patch~LWZJPJ.dockerbuild
12.2 KB
sha256:92993e055821aa00444cb6d95ccd4c6ec68c957b377be8df95e9f83b0783247c
SocketDev~socket-patch~M04NPU.dockerbuild
56.4 KB
sha256:cda0841d63512c81adf6c1e4ec57cb5cc66d5b65923e7a6a03bd97921a32039c
SocketDev~socket-patch~M58KAB.dockerbuild
55.8 KB
sha256:2390e43b9e834b289440230a82bf6956b0fda5b227f04308a752b1ba23b8413b
SocketDev~socket-patch~ML49IV.dockerbuild
11.5 KB
sha256:100d17d60dc60565893260b822de2e0c4ae5db1e871d9bc413cb86aff7bddde4
SocketDev~socket-patch~N1EE1S.dockerbuild
11.4 KB
sha256:c15f5c73c0efeee0e4cdd13a25c22b3abe77291a69f60d2bed11476dfd500e6f
SocketDev~socket-patch~OCI5JD.dockerbuild
11.4 KB
sha256:4886b3fe414db3b4c25dfcdac69e076ae98eefca3f5f0982229ad503e5f94743
SocketDev~socket-patch~P85Q3V.dockerbuild
56.3 KB
sha256:6964746568a420a83d3459259a1acd1b15ff0f7dfe7ce6f680d451a32c3765d7
SocketDev~socket-patch~PN6OV2.dockerbuild
11.9 KB
sha256:31fa8f2dee277bffac697fa73c8be9ad1709471e18fe09cf9281792a95bf0d60
SocketDev~socket-patch~SFVPY8.dockerbuild
14.1 KB
sha256:92ec1c402a8bf9777ba4f3276f065c3763d6a6a49db8aade506679642980a833
SocketDev~socket-patch~TAWTU5.dockerbuild
56.8 KB
sha256:e6ebb99a3904314f5f31aa991ea4fd8bf3e35d26098ad069a434c5eff7a3d78b
SocketDev~socket-patch~TXM9GI.dockerbuild
57.7 KB
sha256:8e59a59b23991941cb2a8a9d672da22b20eb3092613a15cf7f77abd19c664ab2
SocketDev~socket-patch~UIEXA9.dockerbuild
56.3 KB
sha256:7552fc6bdb3a3b9673335e6b8f018c2e646f685d2f40af3b8c7783b480c5739e
SocketDev~socket-patch~V0KHAF.dockerbuild
12.3 KB
sha256:adb71106cc2ceda1361a82518a9a26682980d660fd8f2da36bd460bbb7aeb045
SocketDev~socket-patch~WJ8RU7.dockerbuild
56.1 KB
sha256:1ebdc55dd8c7042792024ed0bc119d72b5e9a496cde21fe0c1a7acc2388a5ad2
SocketDev~socket-patch~WU2265.dockerbuild
12.3 KB
sha256:c6302486d128f3d61adcc36bb960b5001d5a9891aa4dd403136f4ab8b6ef479c
SocketDev~socket-patch~XWKFTD.dockerbuild
11.3 KB
sha256:d614f80dbdee5e18fe2252f903add6897b2b1788d430c535ae6fc3fc499dfaaa
SocketDev~socket-patch~YE0DKM.dockerbuild
12.3 KB
sha256:d49316fbe92646491dae233d810195c268bf24edbfa20c9cf688212e0852ad81
SocketDev~socket-patch~YPWFTF.dockerbuild
55.9 KB
sha256:705217198638ae96cfdb4911aa24cbdc607baa331c820018ecf05773e520ffbb
SocketDev~socket-patch~ZPI4CM.dockerbuild
11.1 KB
sha256:b8406eb2c605ab2817e336c6d98df8ba3e97df8b11f41973e398b2c1ff03dd67
coverage-host
75.4 KB
sha256:aa53525dd1fb2ae44720cbd36163fda1634cb5650b16e3821790f0ab746cf572