feat: package-manager-agnostic PyPI post-install patch hook (.pth) #266
mikolalysenkoci.yml
on: pull_request
Matrix: coverage-docker
Matrix: test
coverage
4m 5s
Matrix: e2e-docker
Matrix: setup-matrix
Matrix: e2e
coverage-merge
Annotations
6 errors, 35 warnings, and 3 notices
|
e2e-docker (pypi)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: DeadlineExceeded: debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to resolve source metadata for docker.io/library/debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb": dial tcp 32.193.102.234:443: i/o timeout
|
|
e2e-docker (maven)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: DeadlineExceeded: rust@sha256:5b9332190bb3b9ece73b810cd1f1e9f06343b294ce184bcb067f0747d7d333ea: failed to resolve source metadata for docker.io/library/rust@sha256:5b9332190bb3b9ece73b810cd1f1e9f06343b294ce184bcb067f0747d7d333ea: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/sha256:5b9332190bb3b9ece73b810cd1f1e9f06343b294ce184bcb067f0747d7d333ea": dial tcp 52.23.22.209:443: i/o timeout
|
|
e2e-docker (composer)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: DeadlineExceeded: debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to resolve source metadata for docker.io/library/debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb": dial tcp 52.205.187.141:443: i/o timeout
|
|
coverage-docker (deno)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: DeadlineExceeded: debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to resolve source metadata for docker.io/library/debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb": dial tcp 52.55.137.78:443: i/o timeout
|
|
setup-matrix (npm)
Process completed with exit code 1.
|
|
setup-matrix (pypi)
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 (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 (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 (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 (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 (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 (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 (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 (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/
|
|
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
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 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 (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 (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/
|
|
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 (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/
|
|
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/
|
|
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-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/
|
|
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 (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/
|
|
e2e (ubuntu-latest, e2e_maven)
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/
|
|
e2e (ubuntu-latest, e2e_composer)
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/
|
|
e2e (ubuntu-latest, e2e_nuget)
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/
|
|
e2e (ubuntu-latest, e2e_safety_cargo_build)
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/
|
|
e2e (ubuntu-latest, e2e_cargo)
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/
|
|
e2e (ubuntu-latest, e2e_safety_pnpm)
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
|
|
e2e (ubuntu-latest, e2e_golang)
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/
|
|
e2e (macos-latest, e2e_safety_pnpm)
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
|
|
e2e (macos-latest, e2e_safety_cargo_build)
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/
|
|
e2e (windows-latest, e2e_safety_cargo_build)
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/
|
|
e2e (windows-latest, e2e_safety_pnpm)
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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
|
|
e2e (windows-latest, e2e_safety_cargo_build)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
e2e (windows-latest, e2e_safety_pnpm)
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~0MXULO.dockerbuild
|
20.8 KB |
sha256:d55816a0cf2dd84d47274213ba5d79ba15c150a9c14c26422c2f5aea0dee5633
|
|
|
SocketDev~socket-patch~1AVSV2.dockerbuild
|
33.8 KB |
sha256:d5bb697480cfad11b968f7a6d68c1fe513ab1971a3ffea20e64dfce0d2eb45bc
|
|
|
SocketDev~socket-patch~1BRFCD.dockerbuild
|
34 KB |
sha256:470bc9dc0a6a9cd763fa6ed1da3777af6193142255a00f563b4088ba93dd1c23
|
|
|
SocketDev~socket-patch~1LPT0O.dockerbuild
|
23.7 KB |
sha256:745285c53490ccae58f7afc0cf29ec86955fcf2602d4fc1b1bca3d6f87349e7e
|
|
|
SocketDev~socket-patch~384GV4.dockerbuild
|
35.2 KB |
sha256:36f86df5f61cf3a42b32f2caaf74eb5c91e3015c727fde946f9fafeca8c82b50
|
|
|
SocketDev~socket-patch~46L98U.dockerbuild
|
21.4 KB |
sha256:ba6fbfe0b84f27f597a7533d4fe0a5f76809bdb095037d8c55c6d25f433e690c
|
|
|
SocketDev~socket-patch~4KXE6T.dockerbuild
|
33.8 KB |
sha256:7e825278015680d715f2fed5cedd3dca5807b2b815d019c02095d6456cf54dad
|
|
|
SocketDev~socket-patch~6CIVJ3.dockerbuild
|
34.4 KB |
sha256:13174d623698990a3a44b2a72ef0617d19781f1ad44a853643d005d2ddb759cb
|
|
|
SocketDev~socket-patch~6TPNX3.dockerbuild
|
33.9 KB |
sha256:a74419cd1df8d1880c783bce0725d5b4449fcf29c74e71d035cdd43fea331c46
|
|
|
SocketDev~socket-patch~8VWTII.dockerbuild
|
9.62 KB |
sha256:f73e6f81dfda73560ab8d81c6a117d3e7cbf767a9e1f527b77d93dea04364fc2
|
|
|
SocketDev~socket-patch~90JSFP.dockerbuild
|
34.1 KB |
sha256:3a2de16e2e6ab76f37f689eb504a60827958dd220a51d5f30993e7cb11459a78
|
|
|
SocketDev~socket-patch~9MF3HA.dockerbuild
|
10.9 KB |
sha256:1b11743dc2f888965c5f1401cab20f33feebee33e14b413f48a39153860b9796
|
|
|
SocketDev~socket-patch~9V2U1K.dockerbuild
|
34.5 KB |
sha256:be141aad22a29b6c31d2cab459e71aa20364903419d54e1e404a9ae9dd50defe
|
|
|
SocketDev~socket-patch~AZZOV5.dockerbuild
|
20.1 KB |
sha256:8c43290513d720883561842c06a47aca52e3f49ccaae15f37cf7b4765a98be29
|
|
|
SocketDev~socket-patch~BKZRFG.dockerbuild
|
34.6 KB |
sha256:09970e3016bbc3d991c8ee9fbc71ba963bf0ab4d9f32b8f49167583dde95b94f
|
|
|
SocketDev~socket-patch~C792BI.dockerbuild
|
21.7 KB |
sha256:88e3b674114d33310ab55b0cef1cef3bf6e3b18ba1c7847a121feda280dbd333
|
|
|
SocketDev~socket-patch~E98B62.dockerbuild
|
34.8 KB |
sha256:16fee504ad5e37284af0aa611aa11da8a1a01e0cb8047a1ab46d090fa7d61e37
|
|
|
SocketDev~socket-patch~FYYXEH.dockerbuild
|
33.3 KB |
sha256:cd27e09e5292146d8e1fabcdce66f310d6463d2e607d55f880026b714f5e5f18
|
|
|
SocketDev~socket-patch~G6BM33.dockerbuild
|
33.7 KB |
sha256:953211b78022a90d03c28f96e1523f9bb2b421ae358d061713a07ee8e51fcdd4
|
|
|
SocketDev~socket-patch~IJ8HG1.dockerbuild
|
17 KB |
sha256:f3984e059bddbee1d20cd0fe74ea38833326090f3472c0879d900f5fb064fee1
|
|
|
SocketDev~socket-patch~JSBA7C.dockerbuild
|
34.1 KB |
sha256:58dd82adb12c89544bd0c19071e4ec3a92e3761275a0714f21da0d64a8e4a450
|
|
|
SocketDev~socket-patch~K7YD73.dockerbuild
|
34.7 KB |
sha256:7f33a34bb4e5d0fc521f304a4d4d85494c077786a8656b33905dccafeeccced4
|
|
|
SocketDev~socket-patch~KRYRYR.dockerbuild
|
34.1 KB |
sha256:c20fcbf41f66a75c3023600aec71b47f434c88bcecdc1232db7fb02d11226a77
|
|
|
SocketDev~socket-patch~L9B1PR.dockerbuild
|
16.7 KB |
sha256:cdec81f171ade7b31207f13421daa7890ebe5a6bb65fa99f2e0aff2fdece4a62
|
|
|
SocketDev~socket-patch~LNFCA1.dockerbuild
|
34.3 KB |
sha256:3fbb1daeddb869c79507d703cf9e8fee3af7c301657899154ab7163f80d82ad9
|
|
|
SocketDev~socket-patch~LZ02IR.dockerbuild
|
16.3 KB |
sha256:30ce619616975b53d10c848d877df60794da8d9b4ec56ebf87acf6419ed74e04
|
|
|
SocketDev~socket-patch~MG4CP9.dockerbuild
|
33.9 KB |
sha256:823d9ded2c266ae7bae04889e9031e46c3fea43990fca5ae28e20bba26e459f8
|
|
|
SocketDev~socket-patch~MY7U6V.dockerbuild
|
20.5 KB |
sha256:e6e8f53d33f061ef0d5afb40db007c8f32944e0123bf131c6d9853293672e65b
|
|
|
SocketDev~socket-patch~NJPJR8.dockerbuild
|
10.6 KB |
sha256:931522fd1fbe8d6a7e42eef26d49fe00ab47dfa4d876159bafc8c1ec333c3d5e
|
|
|
SocketDev~socket-patch~NXH3OX.dockerbuild
|
21.1 KB |
sha256:b83d58e2c0dadb68dde263f7bd713a8da5fd49d798a258e33f6f28b281428de3
|
|
|
SocketDev~socket-patch~O9B4Q2.dockerbuild
|
18.4 KB |
sha256:ff9df1425f56b70a249b6d5cb091917d04dcc18dd4cecf65b13afe2f51d70992
|
|
|
SocketDev~socket-patch~OFFOJS.dockerbuild
|
22 KB |
sha256:09d6280b9808d09cf9ef0099a6a36c1454fea2d5518a5abd14fbabb24f1c9e6d
|
|
|
SocketDev~socket-patch~OGESVU.dockerbuild
|
9.91 KB |
sha256:d1e7712a0c3a8ce822ab4cccd62fd6fb8932f44424c60ab51c7d825d1283fddf
|
|
|
SocketDev~socket-patch~PE8TF3.dockerbuild
|
24.3 KB |
sha256:d17ce5c0c5714310c43756512fa606857eaeb14eead86c7dd7e99800ec7cdc81
|
|
|
SocketDev~socket-patch~Q41ONF.dockerbuild
|
21.8 KB |
sha256:b5ce22b724026dfffbd6827e42bb73293eb1bc8acf274edfd6430754ece59ed1
|
|
|
SocketDev~socket-patch~RF4IU3.dockerbuild
|
21.4 KB |
sha256:8d8a096363a2a0d5b0965c39310052c8d896de3697c1179a47854e9d07d2dd3f
|
|
|
SocketDev~socket-patch~RROEVB.dockerbuild
|
20.5 KB |
sha256:904cb9474fac11e0409eca15492a26f2ae326289bdf5f3ffac05445a5c1f8c8f
|
|
|
SocketDev~socket-patch~RVQEZC.dockerbuild
|
9.23 KB |
sha256:5f8b2ad0419effbb752143ecd69774fee6bc294a3db9fc42ddf502fda3cb37de
|
|
|
SocketDev~socket-patch~SU97HD.dockerbuild
|
21.1 KB |
sha256:70e1d812fb7dda493bdde0118a96622fe51b6e0d7341f71428516ec04fb577eb
|
|
|
SocketDev~socket-patch~SUILZ8.dockerbuild
|
23.8 KB |
sha256:db5ecbf932d84d695a6b8555ca94da3dcfb611cb1674f4c37df180e16ace1972
|
|
|
SocketDev~socket-patch~T5AWHM.dockerbuild
|
34.8 KB |
sha256:0ebaf1761589f4b51986a5aa2a3cf66dffef50bfd1228c2d139e3199a5189634
|
|
|
SocketDev~socket-patch~TWQZGM.dockerbuild
|
33.8 KB |
sha256:89f5f366a7251ba63f4068a2f5fe88939fe16c2a1a5f398c10f5f1a3de88e90c
|
|
|
SocketDev~socket-patch~UQZCNF.dockerbuild
|
34.6 KB |
sha256:b4fbb53005eabea046e2ec67feec7ba28e62f0e0117960badd4a3a5ef7575475
|
|
|
SocketDev~socket-patch~UZR54R.dockerbuild
|
34.3 KB |
sha256:66d3bd8f41692bd73c5c8ea248e0b522489ff4a2c43a3305ef3d64007e46217f
|
|
|
SocketDev~socket-patch~VXW6IK.dockerbuild
|
18.2 KB |
sha256:e83e3140046cb85841e84378f5c5c14f8198be87716e6ca7a8fbcc54ca4e5b6d
|
|
|
SocketDev~socket-patch~WJGRUN.dockerbuild
|
33.7 KB |
sha256:7af3b332e748608483bc529e64e39332361286190f3c2c12a8b51ff0384210ab
|
|
|
SocketDev~socket-patch~WKZH30.dockerbuild
|
23.7 KB |
sha256:16210c170ea96d9d2a2c1faaa5d8e1d04524772d6eec94cd97ee61ef1de2f971
|
|
|
SocketDev~socket-patch~XP1G3X.dockerbuild
|
9.53 KB |
sha256:9f8a599c7c9918cf39db9245ea4e85061b6c9ba09f3d42b6c0ad14d0ae77a374
|
|
|
SocketDev~socket-patch~Y28K0Q.dockerbuild
|
11.1 KB |
sha256:1f1d59325336593bc720dadaace321ccf57f086252ed6244120f5dc0ff1a5fa1
|
|
|
SocketDev~socket-patch~ZXRA5L.dockerbuild
|
34 KB |
sha256:c71b44abd4f72e6cb6ec8587024113c97c1e5f0b799a3f191df808cfd753e022
|
|
|
coverage-docker-cargo
|
38 KB |
sha256:f98a70e5b5735cf916a74c0b05259e56c1d39dc99c0b94108b14d5f64fbeb15a
|
|
|
coverage-docker-composer
|
38 KB |
sha256:bbd16f2290176e62657ce2e906d2ee7eeda0c16fbec1271f3602d671c255538e
|
|
|
coverage-docker-gem
|
38 KB |
sha256:864b07c55b21e599918ea681f8e4396231c9eab019e6416cfadd00671f0ee185
|
|
|
coverage-docker-golang
|
38 KB |
sha256:1e90c55736ca5ce8deee965683496e33eefa87f01b8c2ccecee38ddb6a041c59
|
|
|
coverage-docker-maven
|
38 KB |
sha256:fbe6fc3f4ff342096f1ed776f9eb46f331e124c63bf6c77aaeae9f68b77bbcde
|
|
|
coverage-docker-npm
|
38 KB |
sha256:3e0dca6341b2868d18787e82df094eba5925902c87a8e46a8e8be258530911a6
|
|
|
coverage-docker-nuget
|
38 KB |
sha256:96b215d3ce643bb37f28911b8e60c96a3c6aa8125dc7fe0baa166892304bc0aa
|
|
|
coverage-docker-pypi
|
38 KB |
sha256:4b161adb693ffd1260ad3ea705ef13d0b5037e49f7cadcec096a1a74618b895b
|
|
|
coverage-host
|
130 KB |
sha256:e11757b0b0abf7a343bd8055c34d68b550056ff1d6dcd16ee04f2d3cd6f74e24
|
|
|
setup-matrix-cargo
|
923 Bytes |
sha256:9221c9929dac95f4dc3fa386989e2951465d82e313e166c6a8647b9a4b2af589
|
|
|
setup-matrix-composer
|
919 Bytes |
sha256:b534781ab70181dc4145b4c6e611853b8e1511fecf283f8b0ceac94009407efa
|
|
|
setup-matrix-deno
|
904 Bytes |
sha256:44402f494177ee0ca77b78a4aaf99735af41680d2b3144a06e28a10bf37c838b
|
|
|
setup-matrix-gem
|
914 Bytes |
sha256:3475bdc113697bdea4d575ef0b3716144d19c1a7e3ef40c42655a499c8be061d
|
|
|
setup-matrix-golang
|
906 Bytes |
sha256:ec36812f59e7a1f49d1d6cc278ceef6a384d487700871e3b8bcd2bd7c7ddf041
|
|
|
setup-matrix-maven
|
917 Bytes |
sha256:101633cf4bb976654a371b9544b120adcdc1eb7009692e871c60f8f24b2f5cfe
|
|
|
setup-matrix-npm
|
1.75 KB |
sha256:5f1d7dd26972bbcaaa559121f8f4562d041fa39dfea16df460b898b9755e0c9f
|
|
|
setup-matrix-nuget
|
912 Bytes |
sha256:ef3bc94268352e54b6e441b987270b07b3ef309ac1df2017af3f64731bc681b9
|
|
|
setup-matrix-pypi
|
1.88 KB |
sha256:d32277b9d737864f1062b56208010cbf2926a25d79a9e6c5c046d220b7e6711e
|
|