Skip to content

feat: socket-patch vendor — committable vendoring of patched dependencies #312

feat: socket-patch vendor — committable vendoring of patched dependencies

feat: socket-patch vendor — committable vendoring of patched dependencies #312

Triggered via pull request June 10, 2026 16:26
Status Failure
Total duration 16m 21s
Artifacts 72

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: setup-matrix
Matrix: e2e
coverage-merge
0s
coverage-merge
Fit to window
Zoom out
Zoom in

Annotations

6 errors, 25 warnings, and 1 notice
clippy
Process completed with exit code 101.
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 16th, 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 16th, 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/
setup-matrix (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
setup-matrix (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-docker (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 16th, 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-docker (composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-docker (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-docker (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-docker (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 16th, 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-docker (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-docker (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-docker (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-docker (maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 16th, 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 16th, 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 16th, 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~0G5U0R.dockerbuild
35.2 KB
sha256:0faf829eabca5510d7e8652bde6c4ee5d6f157f3581d7f327415f3c4ee4a38d0
SocketDev~socket-patch~4GDFF2.dockerbuild
11.7 KB
sha256:bafc597c7f599bc4d9c191b49244eaa1e1ccc9311a52407b15d47be5fa526732
SocketDev~socket-patch~4GQNHA.dockerbuild
16.8 KB
sha256:47122d303a6d01e007ae9d10333d2782198e197ec38caf49b074e78d76c89886
SocketDev~socket-patch~4L3VRY.dockerbuild
30.7 KB
sha256:73439d405739e845039d341519d23c5026db2dc29714cc4bbc7d41faa4a62cd8
SocketDev~socket-patch~6RAOG2.dockerbuild
30.9 KB
sha256:5aa0cb9fde463b19761afac1c69edba16d651e6be3b9d43a33db238368a538a7
SocketDev~socket-patch~6YG1AV.dockerbuild
35.9 KB
sha256:390c8e1db0241fcaa5b220d872b040e590169548650e3b8f27d522ed0a091433
SocketDev~socket-patch~8U5JQR.dockerbuild
36.2 KB
sha256:71e9ec3672e4fa7e157cc443c56f21adb319d0f7d64aed5841692ab597f8a8c0
SocketDev~socket-patch~9O10UH.dockerbuild
10.8 KB
sha256:2085af12017b2715dc92a0cff98d2d31fc5c84db78b9fd6c41049e19d2ee5ad7
SocketDev~socket-patch~DD4LR5.dockerbuild
21.8 KB
sha256:58a21bd879e9d779d26a03abcc6ab4ed3ca691222ae566f8ea5ee81cdcc2c3d4
SocketDev~socket-patch~E3WKDR.dockerbuild
24.1 KB
sha256:dde430f07a62958ed73a808180b251cb8b0b54d80128bfd0b987c3cc18b66e6c
SocketDev~socket-patch~EG1YN9.dockerbuild
34.7 KB
sha256:e328ba2553120af6225e91562ed45193b12cab7062f510b24855dc525c8666ab
SocketDev~socket-patch~EQ0BHD.dockerbuild
21.4 KB
sha256:986505ee10ac0d5cace517bdb13ebe70fcf1371cc83b5c0000cf1221cc4dcbe2
SocketDev~socket-patch~H0RDMC.dockerbuild
17.1 KB
sha256:82b3b0ef2a259d2a62571cc217867e18229d856484cdf1296ea697a05f154123
SocketDev~socket-patch~HBVH2L.dockerbuild
23.6 KB
sha256:f1fdcf855a006e64083021e2dd57c64682b659480b1ee2e58f0e54c10cafd17c
SocketDev~socket-patch~HXGQ6E.dockerbuild
35.6 KB
sha256:d7d62ab8de045ce2729a710b9f8eeedb4c8fd883fd5d6445ff6bd6599fb8f66d
SocketDev~socket-patch~I08BPN.dockerbuild
17.6 KB
sha256:072554b96a6cd6473ba334fa2067ee2c15715a9682a190aee7769b9a5f89267a
SocketDev~socket-patch~J1J9YW.dockerbuild
21.3 KB
sha256:0571eaf5deb51a84401b61b6c7d7f0eb06b73c16cd70a9ee9ec6cf3062964221
SocketDev~socket-patch~JAQNTU.dockerbuild
35 KB
sha256:fc535992d15dd7e947486eb50319e1fa5b226e8b3cdf16e86d49c8100f1bb3a0
SocketDev~socket-patch~JDBNYM.dockerbuild
34.2 KB
sha256:4ebaaa0e5aba51f067e6972fe06fe5e82781037fd9eae5bec223b8595aedf34a
SocketDev~socket-patch~K2JEBT.dockerbuild
34.1 KB
sha256:94dd4bdd228ba47b43353a3a6ebe67c07fd3b1c66ad12db934eb7098d99024ec
SocketDev~socket-patch~K6NFGK.dockerbuild
22.2 KB
sha256:39d1bd2067bb19c3625404b06eb231124ad229e80b09f46fb538a5a5f5aeb04e
SocketDev~socket-patch~KGZ4F8.dockerbuild
21.6 KB
sha256:0683e9e2e175320a5d585c79c0343a85bfd1d732472e30e8590e443fa179c7c3
SocketDev~socket-patch~KT391O.dockerbuild
34.8 KB
sha256:5c0a91674162c0da1a349ba2fe7d4787de0725a482d89b34a45bf33b5830378f
SocketDev~socket-patch~L96JEF.dockerbuild
24.6 KB
sha256:4fbc4aecbb0cbb909a83efca4341c66281d6b9a0a97b2609219268c2666b6135
SocketDev~socket-patch~LN6IAW.dockerbuild
25 KB
sha256:95f1f13347fd9f8502091d12a797b89a3ad8d4255f255ddc42ba2cd0b22d8c52
SocketDev~socket-patch~NE5REE.dockerbuild
34.9 KB
sha256:676e5291b029c7c62f46314f3ae42fdcf54be216ade67bf2b4c4d0d9f028f156
SocketDev~socket-patch~NGOV11.dockerbuild
33.6 KB
sha256:0f24c2408729b67a6a190cb386b84413285ad2661adbc328df5b97ecfb68b81f
SocketDev~socket-patch~O6S44Q.dockerbuild
34.3 KB
sha256:f2f92df412f855b025892baac395b31202ddb1dcc249fa8620d8f54ec0fba275
SocketDev~socket-patch~OP74KI.dockerbuild
33.9 KB
sha256:25f51b679f626d133a1f5aab9db6dff978f861df0211b60edcb0cefba293e803
SocketDev~socket-patch~OV9O78.dockerbuild
34.9 KB
sha256:1d293f0d30529d4cd04625c97b19d14602ee94bc7af2edd7f4f03ffd130114cc
SocketDev~socket-patch~PGVXEN.dockerbuild
21.3 KB
sha256:461c58bdea74f474f01d416df100eb2c9752fdf1b8a4c284a8dc5f4daa89194d
SocketDev~socket-patch~PWGPUW.dockerbuild
34.6 KB
sha256:d56f3efb61a088affe4a0516669b3821014fbf69bc7369e4926e517178009632
SocketDev~socket-patch~Q3GINI.dockerbuild
34.6 KB
sha256:40abc776c444b52ffb546fe1c66e3eda136f0a9dc8b1e01b167a9204df19b0c5
SocketDev~socket-patch~RH85Q5.dockerbuild
35 KB
sha256:b5117914b3671fbef565866611f78dddd00008c833df77b5c80926a793b0175e
SocketDev~socket-patch~RJ9FQ5.dockerbuild
34.7 KB
sha256:980cb1bc1ab820059bcfd06b7ba31688430a01abc271491952a8046e2d2b727e
SocketDev~socket-patch~RXGQMF.dockerbuild
18.2 KB
sha256:5a53fbc90d5dcc3053522fe290a1fb916f1928f26ba32b9fde8b062626ff85f5
SocketDev~socket-patch~TNASOQ.dockerbuild
35 KB
sha256:00a2dab3e092cc76904ab94cbe9fb3e26394b64e8468a5506e947837e639bef9
SocketDev~socket-patch~TSZAY1.dockerbuild
34.7 KB
sha256:e58c4fbe363b57f93005bf59fb459b272b7b43ea0fbf069c497958eba3dbe20a
SocketDev~socket-patch~U6O7UT.dockerbuild
23.2 KB
sha256:39db24d5175d3d269a9d54eb6afa2be73417479065bc9ea05ea42a61907ba0b4
SocketDev~socket-patch~UAWMYB.dockerbuild
34.2 KB
sha256:1826be98e2293b06dd44aa9a068dcef572d3aaa701ad33dcb3e3701c1f37d436
SocketDev~socket-patch~UFMMC9.dockerbuild
18.3 KB
sha256:59389c64b8a9380b7bd18ac6fd76cdc92777488d75a2656bb248716fe03b9c67
SocketDev~socket-patch~V4KXES.dockerbuild
29.4 KB
sha256:bd88e7319f91baccd462a5971d4c3ed0ca8ee5e2df679e79e56e66cb1e98456c
SocketDev~socket-patch~V9ND14.dockerbuild
34.6 KB
sha256:48f3edb949a8f244824e5e2aabb1e0a01543a5c09e8c305399a94c0df3d65259
SocketDev~socket-patch~VDVP1Z.dockerbuild
18.6 KB
sha256:e0d2c9f403104f50f67c31a93e35208162871e470233d4da0f66677f3b70753a
SocketDev~socket-patch~VFZA9T.dockerbuild
34.7 KB
sha256:588867af4f2b98431c3cdf7a9c3c6471ab835920219cad74b47513da372ed607
SocketDev~socket-patch~W43IZY.dockerbuild
24.6 KB
sha256:a362a0528eabbab3b69ab51220faf2dc75ff5a2195d0789dc26a88efbd381215
SocketDev~socket-patch~W49VJO.dockerbuild
21.9 KB
sha256:3d634f642f5a9c51b8017ab5424d7466a987f67df0687a35fe234f1b116580a5
SocketDev~socket-patch~W4WNQJ.dockerbuild
34.9 KB
sha256:cf662274b23177670eb418b069fd26b506156f7b9be1ed33761afb49aa0ec0fc
SocketDev~socket-patch~WIZEFN.dockerbuild
21.9 KB
sha256:57ed67d1b474fb849531d973891f0f4edc6cf0ac0d960f33537a4820bbe50006
SocketDev~socket-patch~WNCFVO.dockerbuild
34.9 KB
sha256:26dffe8b97dff867c5e8c82a2645d06b8e6fc200c58077a617599398365be47b
SocketDev~socket-patch~WP535M.dockerbuild
35.4 KB
sha256:038dc4e54482cc3ba86adbd21d8bfecc257a029d79cf057ff1855b56e90490fd
SocketDev~socket-patch~WXF9Y8.dockerbuild
21.5 KB
sha256:0236c0778dcd9bba00f7e6d44d733789e83bd10b9f873ee7ac2b779f00c03b4a
SocketDev~socket-patch~YEHHY0.dockerbuild
11 KB
sha256:4fe693907171ffc561abf7f1ed6e63a5b96262e0ab9f0de55c7bbc1e3bd01cce
SocketDev~socket-patch~YG58NO.dockerbuild
35.4 KB
sha256:b63eccd7e08dd43339d360da88aa2e8e54be26e05873e96aea841d521009e44e
coverage-docker-cargo
74.6 KB
sha256:b5d5c238a98ee1e8d6662af098c2c2c65f2aec4e1cd8cf516d0ba904b3eb9f7b
coverage-docker-composer
74.6 KB
sha256:5cde8fd8e15e97d39642bed8f23e2ab02ebf55e438b85181a9765aa85c5e15a5
coverage-docker-deno
74.6 KB
sha256:5913a0491b820646dcaeefe99b5f497b33e703c72a54a46853c6cc1707b07b88
coverage-docker-gem
74.6 KB
sha256:e642b2a74bc294bcfba9db08a0fb156017fc266f4b3cf05b9b016dd04c0713e6
coverage-docker-golang
74.6 KB
sha256:2470a236e825818acbb704104f4a4b9540aee76f243f6206ef873d828360cb32
coverage-docker-maven
74.6 KB
sha256:fa3c64aea0531d5afbc15b5a7abf4a513f816c010bd0d37b493b6d59c4cf4768
coverage-docker-npm
74.6 KB
sha256:50dfe5cdfd83b73ce4216c9340f6d61921aa7fbbf7e3a2c594b146655e5cbd39
coverage-docker-nuget
74.6 KB
sha256:c68fba5ecce0bd11e4b01f1a5c602c722eb03a1257a73efa0d1eef14df9f6171
coverage-docker-pypi
74.6 KB
sha256:753b078b9b6c567fc35f0df245218a4c7817d61ad80c6ec38c311691bd9d9839
setup-matrix-cargo
930 Bytes
sha256:186004c00074a87920195d89d43f77b3fb01df0dac6ac2811fb49fb31ed3d088
setup-matrix-composer
918 Bytes
sha256:750c66bb14eae14e40aafb10132215be674e2618f7b2a9ee3b2143f530fe1b9e
setup-matrix-deno
905 Bytes
sha256:e1b5c500dc1031c43684fdfedbb1a1b2a52adb717bb2cac0bc5d0932f981ef74
setup-matrix-gem
923 Bytes
sha256:a5a6e824f109d8149e4b526bd662dac23c52c8be5d9581436cfaff097a9555b7
setup-matrix-golang
907 Bytes
sha256:db270eefc8e29efc51d9318c79a67031aaddff8d1afb34e6a9b4246fbb5f4c3b
setup-matrix-maven
919 Bytes
sha256:e6f8baf613ce651a5741155958f6e43a66970588300298301ad259e1ffa416bc
setup-matrix-npm
1.76 KB
sha256:62ef593cf45e5a0093092a2fb744459461f23557d34914198e2fb2dabb157a81
setup-matrix-nuget
911 Bytes
sha256:c3921555d25879c74b79d5156bc2b991f78bcf07fa88e3207faec0e9fdf777d6
setup-matrix-pypi
1.88 KB
sha256:87fbe700b19b6d472af3e962b19e231930cc8827bb9a9d4843b357bbd2b500f2