Skip to content

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

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

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

Triggered via pull request May 21, 2026 23:24
Status Failure
Total duration 8m 21s
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

20 errors, 7 warnings, and 1 notice
test (ubuntu-latest)
Process completed with exit code 101.
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
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
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 (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 (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 (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 (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 (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 (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 (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
test (macos-latest)
Process completed with exit code 101.
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 (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 (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~44IKHM.dockerbuild
56.9 KB
sha256:cf6048d5727de3c75667e3ac27d078e7d530676f12a2e90fd78fc09493e7b744
SocketDev~socket-patch~8LYO87.dockerbuild
55.2 KB
sha256:bec99f1e168ee7477e00a0b4cd654a91dfd11f254fc113efb32e879fe090cc8a
SocketDev~socket-patch~97TJ4M.dockerbuild
14 KB
sha256:7629d65cabea2178441a26fb48bfd2242ab05d9e64dc168b697b257b79258369
SocketDev~socket-patch~CQM5KZ.dockerbuild
55.8 KB
sha256:c708739d6a901fcf4385ef4c6770348ce1a8f76b657ef3254691ca1f35df3044
SocketDev~socket-patch~DS12OV.dockerbuild
11.6 KB
sha256:cd38d74cc08b13a3639e0887d7610577badd8f9e32900c961e3f43f324c27582
SocketDev~socket-patch~F2GI0K.dockerbuild
55.5 KB
sha256:bb25262f99b91e5754772fae1d4ece0a7309e1e7488df05b789144851349b0c9
SocketDev~socket-patch~F812I3.dockerbuild
11.3 KB
sha256:fd6594816ee76a47170306f11df2ffb764ecc498b5f4cefbf4fa075ef9e2008a
SocketDev~socket-patch~GCFW6G.dockerbuild
12.2 KB
sha256:9087f34c5ca1a38c7dce0af1c2f5c4e0efe95386718056ad8ad683ff15826ebe
SocketDev~socket-patch~J37A5C.dockerbuild
11.5 KB
sha256:6da458326502763a55da0ee80300e59e7ce8b480f52c79f18b212016ec178498
SocketDev~socket-patch~J4LA72.dockerbuild
11.5 KB
sha256:cb39e6d779cb41a3db42ade53d5ba6a019657c5b44960da5fb8a94f239bf510c
SocketDev~socket-patch~J5D978.dockerbuild
13.4 KB
sha256:e75dbf191631f1e1ae70c22fc2a28e6a110bafcc90023aa988649d16ad62090f
SocketDev~socket-patch~KCOXU0.dockerbuild
55.2 KB
sha256:28bf1fc41d59183fd01b77cc9588ff8e3ded36380630048a524f3801126191c2
SocketDev~socket-patch~L2QIWY.dockerbuild
12 KB
sha256:182e0fedd61096e60cb7ef655154ff1ff963b33ac1a4b662fbc9ce25f28a26cb
SocketDev~socket-patch~LX1NJR.dockerbuild
11.3 KB
sha256:c01fbd6fc4672381f12db5c50ea5f4980c6c15e5f905e0f93322fbcb87914000
SocketDev~socket-patch~OUHVOU.dockerbuild
57 KB
sha256:af598d8478ac00418066ad7e8968adc1e5a983f91b3f3195657d2a8190569f74
SocketDev~socket-patch~P2S1VO.dockerbuild
56.1 KB
sha256:daf87fc9788bee47c5c175c8c746055775e7548f621c3476f4822bf78081cda5
SocketDev~socket-patch~QCJ1IL.dockerbuild
57.3 KB
sha256:67402b029926dbd79ea55d4133b7636793df09b39f5fc17ebc23ce4626c315f1
SocketDev~socket-patch~QDMM90.dockerbuild
54.5 KB
sha256:e9c1051e0cc60a660d2f3126f351662ff77b2aef7e7881a838c1e86661c7a439
SocketDev~socket-patch~SPNM7E.dockerbuild
12.2 KB
sha256:5b601f497c83acbcb4aa10c20fc5260f4599271880578db63db17f0c6a2793d3
SocketDev~socket-patch~T40B7O.dockerbuild
55.5 KB
sha256:e51b61e81ba541477663b6a2fb6a77db702feb60e02c2fe304a6b0b94cadcd16
SocketDev~socket-patch~T5ZZPC.dockerbuild
11.7 KB
sha256:70124b9464c6e906852d5b4c94bc08fe28f27bd5dc66705f8c6e2de2bdb3a0aa
SocketDev~socket-patch~TA4IAM.dockerbuild
56.8 KB
sha256:78cdf0921133183ef1d5c74d7cb3c061a20ae5dc7bb851f74dd09f63f738af59
SocketDev~socket-patch~UXMOLI.dockerbuild
56 KB
sha256:6d4add6bba85b8b83c9ccd4941b8d079074cf5fa868aa4a797880e4750ca1837
SocketDev~socket-patch~V69VYJ.dockerbuild
11.4 KB
sha256:1db5962257b2e098fe5c26b625014e6e440c68b71426d8d4d86134c692fda97c
SocketDev~socket-patch~VCFZYF.dockerbuild
12.5 KB
sha256:7b803551c69e13ee0e178792c4764ca7e502b6970cbfc840fa08eefbd920d9af
SocketDev~socket-patch~VXZ84F.dockerbuild
55.8 KB
sha256:0018ddd67af720f45083feb3f7a9bd06dafb01159d67863a5699e4097afb64a9
SocketDev~socket-patch~W2OKP1.dockerbuild
56.2 KB
sha256:44022b733016560addc61a57df22519b9dda3b6c38f6cfda22102d527f3e65be
SocketDev~socket-patch~X0SLBS.dockerbuild
11.3 KB
sha256:f21ff92710b606e061aa37fd8b3be5e089cea7fe0b734ee4e92191458fc12ea2
SocketDev~socket-patch~XSSOTV.dockerbuild
55.6 KB
sha256:806cacf6f17d2f5c39595c807b39b4896c605429fd20c941bd72f0ed969d5ed4
SocketDev~socket-patch~XWZI6J.dockerbuild
11 KB
sha256:439d7e1f9989f08d081fd421ee74fd47f7e1a3b1b764d3c69b1bd78ae769906e
SocketDev~socket-patch~YIIHCW.dockerbuild
12.1 KB
sha256:297a5c85ec1b0ab7eb04738281500dc11674686ce7e5b0540f0ec5dacf24752e
SocketDev~socket-patch~YJDRR3.dockerbuild
55.4 KB
sha256:a7e2715cb5df315378de210e01c8fb6fccdfbf6543411f29ac250f82a4c599d7
coverage-host
75.6 KB
sha256:a3469b6f121ed4eb465cacd0fc803161e141fbac09badcc69a1b5e90531b6e18