feat(setup): fix cargo release blocker, close all 5 contract gaps, add composer + gem publishing #292
mikolalysenkoci.yml
on: pull_request
Matrix: coverage-docker
Matrix: test
coverage
1m 23s
clippy
26s
lint-ecosystems
16s
test-release
2m 18s
dispatch-tests
12s
Matrix: e2e-docker
Matrix: setup-matrix
Matrix: e2e
coverage-merge
Annotations
32 errors, 25 warnings, and 1 notice
|
e2e-docker (deno)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (composer)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (golang)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (maven)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (npm)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (composer)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (gem)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (deno)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (cargo)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (nuget)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (npm)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (golang)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (cargo)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (maven)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (maven)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (npm)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (nuget)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (pypi)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (cargo)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (gem)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (gem)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (golang)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (composer)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
e2e-docker (pypi)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (deno)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
setup-matrix (pypi)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage-docker (nuget)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release --workspace --all-features --locked --bin socket-patch && cp target/release/socket-patch /out-socket-patch" did not complete successfully: exit code: 101
|
|
coverage
Process completed with exit code 101.
|
|
test-release
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.
|
|
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 (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 (maven)
No files were found with the provided path: report-maven.json. No artifacts will be uploaded.
|
|
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 (npm)
No files were found with the provided path: report-npm.json. No artifacts will be uploaded.
|
|
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 (composer)
No files were found with the provided path: report-composer.json. No artifacts will be uploaded.
|
|
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 (gem)
No files were found with the provided path: report-gem.json. No artifacts will be uploaded.
|
|
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 (deno)
No files were found with the provided path: report-deno.json. No artifacts will be uploaded.
|
|
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 (cargo)
No files were found with the provided path: report-cargo.json. No artifacts will be uploaded.
|
|
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 (golang)
No files were found with the provided path: report-golang.json. No artifacts will be uploaded.
|
|
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 (nuget)
No files were found with the provided path: report-nuget.json. No artifacts will be uploaded.
|
|
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/
|
|
setup-matrix (pypi)
No files were found with the provided path: report-pypi.json. No artifacts will be uploaded.
|
|
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/
|
|
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 (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/
|
|
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 (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~0QVGE8.dockerbuild
|
19.4 KB |
sha256:80df9486bc806106ed6f19db38fa3784d31cb6101042693e13db2968ebd4365b
|
|
|
SocketDev~socket-patch~6OH7GU.dockerbuild
|
19 KB |
sha256:bd746e4ad96cad34d3fa44008bcf5429e0f098b228a95d5afb8f93e55bb1d9f0
|
|
|
SocketDev~socket-patch~75ONQH.dockerbuild
|
19.3 KB |
sha256:9bc0a7d90f5dd966c9a73729e2dac2b628e3d2ea92c52d6c5a3b211fe7cd9f76
|
|
|
SocketDev~socket-patch~BOW9QQ.dockerbuild
|
18.9 KB |
sha256:07c67e4b9fca2c19c96ca89b223634121c854b884f6f67d71133bb369aaaba67
|
|
|
SocketDev~socket-patch~CEPYJN.dockerbuild
|
19 KB |
sha256:41840e275009ccaa532131f42961cef8073c98364cc08e62b5b6000703b1a31a
|
|
|
SocketDev~socket-patch~CLMWSF.dockerbuild
|
19.3 KB |
sha256:b0056e95b966f5c26a2255dea2d631da51918467cd8beefb239e9d7480a4d42c
|
|
|
SocketDev~socket-patch~DP574A.dockerbuild
|
19.5 KB |
sha256:3b85a652e028e43c132a9edcf613f7508f8bcc3907bfabba91a5c87aeab2629a
|
|
|
SocketDev~socket-patch~EOZ80C.dockerbuild
|
19.4 KB |
sha256:f525c5730673a6fe044fc67cc7371395e44184f1bfd0979fbd8693dde1942303
|
|
|
SocketDev~socket-patch~FJLXMK.dockerbuild
|
18.9 KB |
sha256:948efaf76ac260b4aebd5ecdc663b42126e9ad39e6cd0934aeb665eb136131aa
|
|
|
SocketDev~socket-patch~J0HT19.dockerbuild
|
19.3 KB |
sha256:83768636dc81b598eccf88e750893fa87ff829f5c23f2782799e0018f284cc8d
|
|
|
SocketDev~socket-patch~JA84KH.dockerbuild
|
18.9 KB |
sha256:31b605ac75892220fc6eea08435f1da1a1e3a1980c423f2ebe40d8e022f8fa57
|
|
|
SocketDev~socket-patch~JOIAVB.dockerbuild
|
19.5 KB |
sha256:620a885c12fa8d3edd9bb124ff0d3a6ec3b2849c24255ddc65439f8324abe06d
|
|
|
SocketDev~socket-patch~JWRH4H.dockerbuild
|
19.3 KB |
sha256:a1834764763c7805812c9487a93e8b59df447af7661151f434e446d5276f9cdb
|
|
|
SocketDev~socket-patch~LX5U98.dockerbuild
|
18.7 KB |
sha256:71c68eed59d065979981edfb3ce95a0dbc355dbec0e5ed081e13d30216454e3c
|
|
|
SocketDev~socket-patch~LZPM6U.dockerbuild
|
19.3 KB |
sha256:9fdcf9fff20ed1cf2101d10ca6d5a741c67d86670ea140280d1863a5003484d0
|
|
|
SocketDev~socket-patch~M4HUGW.dockerbuild
|
19.4 KB |
sha256:47fb0685efaa67b30dabe0f676307864df492b0e8724083d0850720aa0954e28
|
|
|
SocketDev~socket-patch~NDDQSK.dockerbuild
|
19.1 KB |
sha256:ee4d764fed1b1b7f43d9348667adda0b4b14e19caf5adc843c77734a5ee38ea5
|
|
|
SocketDev~socket-patch~NLYBLP.dockerbuild
|
19.3 KB |
sha256:93b2660abfac24c84419a393165663b3e57f31513e6314c7ce76876daea4d2bb
|
|
|
SocketDev~socket-patch~NYPAN9.dockerbuild
|
19.4 KB |
sha256:0340dcb8169a1cad8c9735ba135292536f9555034bdbfe12c3a5a0033142a562
|
|
|
SocketDev~socket-patch~OJX9T4.dockerbuild
|
19.5 KB |
sha256:f1be5e80cc5e58cac036c86c3f38091bf0da08d3470186fe689ad7fbd772ff2c
|
|
|
SocketDev~socket-patch~PDEYLX.dockerbuild
|
18.9 KB |
sha256:05faa3e5488bd684b58f0d6dbf15c263c0ff4f98150fe99e21ef8698051b11ad
|
|
|
SocketDev~socket-patch~RR39L0.dockerbuild
|
19.4 KB |
sha256:4a9eb694dcc0b76ea67832bb0e800eaa454f33351c1768ad2fb37d6af7afbc62
|
|
|
SocketDev~socket-patch~RSZBX1.dockerbuild
|
19 KB |
sha256:f3749911adf80ae68c4d423c8b05131a1c41cf2be5fb0b04dd62a2e41fdb2fee
|
|
|
SocketDev~socket-patch~SVYW40.dockerbuild
|
19.4 KB |
sha256:bd9cc08410a20f88fae9408a0a1cabd0a06771c0c0b7e3ed5103d4bad21384b1
|
|
|
SocketDev~socket-patch~UUFXAE.dockerbuild
|
19.3 KB |
sha256:dff1f995160f85fff87b8aaf0e0b9db7d33c8b8bb6367367fac1eb6f16d88ba5
|
|
|
SocketDev~socket-patch~UZJXUT.dockerbuild
|
19.4 KB |
sha256:d9ecf87d83fd53268ebeb9985e000820d22a514dce0e026cab186c91da4fc87e
|
|
|
SocketDev~socket-patch~VEW0I2.dockerbuild
|
19.3 KB |
sha256:a9b2e2a3061a2cb7e9982e69d66803dc25955218b3b36f6a9d8f45d8b320eebc
|
|