Skip to content

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

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

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

Triggered via pull request May 22, 2026 00:53
Status Failure
Total duration 7m 50s
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
coverage
Process completed with exit code 101.
test (macos-latest)
Process completed with exit code 101.
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
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 (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 (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
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 (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 (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 (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 (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
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 (ubuntu-latest)
Process completed with exit code 101.
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 (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 (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
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 (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
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
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~31COHK.dockerbuild
49.2 KB
sha256:9094ae01976b92a69a072e699574d61517b622d2c45a98bf09a33850fff2b1a7
SocketDev~socket-patch~3SC7O0.dockerbuild
48 KB
sha256:d1b69d68195f5e2ca3605dfb4b45c34aa874537a1f081d955bb23a704b354f18
SocketDev~socket-patch~42UMQM.dockerbuild
11.4 KB
sha256:7b261fa485ce47761bfe2b4437d01284abfc5ccf1ffccfd5a3716e934b754da7
SocketDev~socket-patch~7J9PVI.dockerbuild
47.3 KB
sha256:9341afa05d6c0a0a7e03681a4efc8f18a578ff9f8cd6d96f6ab7d367f4242061
SocketDev~socket-patch~91ITA6.dockerbuild
12.3 KB
sha256:e76d22ab8c977ade7a9f8900bc41d74af866cee2be2ca50ba1e95f7bfaf3c9c0
SocketDev~socket-patch~9E9DSC.dockerbuild
12.2 KB
sha256:83c2e1e03abb55f1591f9efafbb4b14084b8984e2f13f520592dbaeaf53abe78
SocketDev~socket-patch~9L9DD1.dockerbuild
12.1 KB
sha256:80c41beec69b75a859c05172e35f32e4d8167229804e5c77d862602538c0a793
SocketDev~socket-patch~C1SN1J.dockerbuild
11.5 KB
sha256:9e09eff5458b7ea8ce835dc96b1b5428a628f1ebe8387dbfa8821ff8449875e7
SocketDev~socket-patch~CU2D78.dockerbuild
47.2 KB
sha256:0ab7368fc5df66a70f73becee85dbcca7c2b1a449cc54845a8ab61827b474932
SocketDev~socket-patch~DV7B33.dockerbuild
47.9 KB
sha256:4d84af3dbc63a43da77ad4ace8c70c922a6f6c692683fea8b2e04d70ba5a8e46
SocketDev~socket-patch~E7LUPN.dockerbuild
48 KB
sha256:722ce85311357a9dc566570f8933e18ab3ec69467f33a7ad30a06bd5d91508fd
SocketDev~socket-patch~H8HDA9.dockerbuild
11.4 KB
sha256:5efd479abcf96a302b30ba4ac78e0d3c108bf1fb40e06ab228e3dc6b0d1ec5e1
SocketDev~socket-patch~HZKP7R.dockerbuild
47.8 KB
sha256:d2cc8493c61dd3d09d6a8ac95aa87745d8e0a7173ec5eaa5651f03fd000c129a
SocketDev~socket-patch~KE6JZO.dockerbuild
11.2 KB
sha256:671bfff4a07dfa3768f12274c17c4bfc814cdade91ba56ca6e0f9b57d15044e9
SocketDev~socket-patch~L9TQM7.dockerbuild
13.5 KB
sha256:77eac0e9ec7ae935671edae8f20ac7fd84a8918dc611e54dfce0221d9a413ef8
SocketDev~socket-patch~LHFXLM.dockerbuild
48.3 KB
sha256:40736e8011e752271e4f672e91337ad01c9c6b894454da16162b19f4d07630e1
SocketDev~socket-patch~NFDQA1.dockerbuild
11.6 KB
sha256:46b0887bf51b673e67f28c871c5229e6eed787d8872f6ca10ded8d651a409755
SocketDev~socket-patch~P2CZIE.dockerbuild
48.1 KB
sha256:276631d683dcce02bba506835652ca0e27023eb9d4f7646641bdde52dce7114b
SocketDev~socket-patch~PJVDAM.dockerbuild
48.8 KB
sha256:97e005451929a6e4216f6cb3a9f103817efa89bc57c48d51ea868a9db7938049
SocketDev~socket-patch~Q0OIVG.dockerbuild
11.7 KB
sha256:f683d47e99c7c8c3bdded32dab3dc17bf1d5e438f460661f312c3b22d99ff574
SocketDev~socket-patch~Q2UJRZ.dockerbuild
11 KB
sha256:4d3562102657e4066286fe596b44dd844ede4d6f6a5767ab06abfe3cb62aa7bb
SocketDev~socket-patch~R5DINT.dockerbuild
12 KB
sha256:8c48fb6839b9452550bfcf65820909919abe724e61ed79fe1cdfc34c0cf6018e
SocketDev~socket-patch~RWTAH4.dockerbuild
46.9 KB
sha256:c8a2dffa6c55476128a17a3d0c432174be055d892a22d748129aef974fe09a51
SocketDev~socket-patch~RXMXCE.dockerbuild
12.2 KB
sha256:e7c577dcfb0496b58d556694f9e11727535489c8bc4c8318f1a845f2584d362b
SocketDev~socket-patch~S5V4SY.dockerbuild
48.2 KB
sha256:e65d8f35df07bd7d799214f2fee421bab2f8fb0ee81e6c4a700dad6dc3180720
SocketDev~socket-patch~VE4WSL.dockerbuild
48.2 KB
sha256:a4a33e9fd4fe2ccdec014c4774a4b1db54dfd5335024d205a79b22b9f94bf1df
SocketDev~socket-patch~VHASYH.dockerbuild
11.2 KB
sha256:330c1c87909416c8b9e97374c23c91dbc9925089419d6cef59e070b14b8e8fcb
SocketDev~socket-patch~W9PAG8.dockerbuild
14.3 KB
sha256:334a9acbfb99755154e64a7b213178caa8f67c9f5d1d284f68f904ca2c68d17e
SocketDev~socket-patch~WVN792.dockerbuild
47.8 KB
sha256:2ead662dc24cd18f6b75d530179079db787b87bc27863e3cb8fdb39458fa14b1
SocketDev~socket-patch~XOM1ZB.dockerbuild
11.1 KB
sha256:e7b617edb59a0ba97ac725f649a2dbda9be1be322a1e88455f255905f7571eda
SocketDev~socket-patch~Z1DBPF.dockerbuild
49.7 KB
sha256:77c42e6c343fc2f5d26c3c71b21aa23d2e80b10c26a15abc4becd710e10e1c18
SocketDev~socket-patch~ZZHXUK.dockerbuild
48.2 KB
sha256:67653380bb03c6ac0b899a1dcb863f75f30d73a8b8f9e529cca341e696f31448