Skip to content

feat: package-manager-agnostic PyPI post-install patch hook (.pth) #264

feat: package-manager-agnostic PyPI post-install patch hook (.pth)

feat: package-manager-agnostic PyPI post-install patch hook (.pth) #264

Triggered via pull request June 2, 2026 22:39
Status Failure
Total duration 22m 56s
Artifacts 71

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

3 errors, 35 warnings, and 3 notices
coverage-docker (cargo)
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 3.216.216.166: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 (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 (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 (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 (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 (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 (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/
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/
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 (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 (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/
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 (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 (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 (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/
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/
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 (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-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)
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_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_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_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 (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 (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 (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 (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_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 (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~12Z7GL.dockerbuild
23.7 KB
sha256:5baf38d9c06d2d8fa99586c52af9efbf56bf31b8960eb201aaeede998000a695
SocketDev~socket-patch~1Y915L.dockerbuild
22.1 KB
sha256:ea83b885c86b48d11b9987bd46ba7d3054ce6297ff5b858e0014fec27c2f9a1e
SocketDev~socket-patch~4MHZ1J.dockerbuild
24.3 KB
sha256:6fe74762202bfd00000340fda09653dd3262d003658ad8148950db6ec4a2f59a
SocketDev~socket-patch~4ZOLOU.dockerbuild
33.6 KB
sha256:bfa8cd0fb95df320a95a42227c458cf0a21940d7c1d5a6889a13feb1c0115a31
SocketDev~socket-patch~5EGQ72.dockerbuild
34.3 KB
sha256:f3e6656dfde8cb24b3ba969ce297873ef1219beaec16abd1a9c169e3078eabae
SocketDev~socket-patch~5F4JC7.dockerbuild
33.2 KB
sha256:06397e2551ed66c5c68cee13c0249bf814dd9734b5f870800468f93039c129e4
SocketDev~socket-patch~5LMSAH.dockerbuild
33.3 KB
sha256:4d931f8a3f4c17566f1a0c48667a45375da7c9de0c9de372f4369e37af4c4f0b
SocketDev~socket-patch~5NV74Z.dockerbuild
33.1 KB
sha256:017edfb4510bb6326175c39752fcafd367f644959024fe7e784649f37e733118
SocketDev~socket-patch~5S7L0C.dockerbuild
33.8 KB
sha256:b800cc87b659397f712c105504aaa9ff344141ef61903a36d3174bd2dc213143
SocketDev~socket-patch~7RASIK.dockerbuild
33.7 KB
sha256:52e91d66cf6648c3b1fd6b5895c45822ef851e1835457c12458c24d2072233ad
SocketDev~socket-patch~8IQYYN.dockerbuild
34 KB
sha256:41e97803eb97cfb7bc2cbdc5e6f64e1c2228bf0ff345156f0a24d191da604147
SocketDev~socket-patch~9CSG2X.dockerbuild
20.5 KB
sha256:cea39673012e2bde40171fee9a275dc6435b07bc2e3996849dab9572bbe0fed9
SocketDev~socket-patch~ATHZD6.dockerbuild
34.4 KB
sha256:37ca83ae94e1f48d37566ec12da2c99fedf050dbf807c3c04bc10f0b32e6011a
SocketDev~socket-patch~C6RVHO.dockerbuild
33.4 KB
sha256:3bacb2eaad806307b501b9d853f7bd002e5f14cfdff03be1622b74a1554681f2
SocketDev~socket-patch~CVFRVI.dockerbuild
23.8 KB
sha256:d258d474a3d2a52f2ac208aa865b9bf91d038c83152d15ea72d9654f5c23f3a6
SocketDev~socket-patch~E3DKDT.dockerbuild
33.2 KB
sha256:a920a287f1f761455c2cafe1549d089ebf92ccdcd83f767cb6378503920dd27d
SocketDev~socket-patch~EYYK2L.dockerbuild
34.3 KB
sha256:5b9e4fed329a10be9ab1e03c316398274664f554375d30fb25f33107dafc4cc4
SocketDev~socket-patch~H71NMG.dockerbuild
17.4 KB
sha256:bc8877eab2818516a737df358e465241d3c7c79d6a2e2b074f32658ed920d790
SocketDev~socket-patch~H7ZMO3.dockerbuild
21 KB
sha256:28533cf87ccd4d275625a1127942090ef8b1f53b0abf80845d3052a2d68b53e8
SocketDev~socket-patch~HPUX8J.dockerbuild
20.4 KB
sha256:7822f021d6a13f455395e7b6c37527a0b6798f5707681bab4c726a8e82da6e12
SocketDev~socket-patch~I3NJUG.dockerbuild
32.9 KB
sha256:fb86c091791ce6d3096c22874e446518ee21450f5efdc506f26188bd0a669f5b
SocketDev~socket-patch~I40HQC.dockerbuild
19.7 KB
sha256:784a69f55c6b8bf2291cdfb2848b8d3404418b4ca8c29b1ab15c116cf0140a47
SocketDev~socket-patch~I6OFKA.dockerbuild
11 KB
sha256:51ed19f4e6ddbf47d6906e0a794c0430ac279951fcecdd2642decdbc3053b2d8
SocketDev~socket-patch~IC1Y81.dockerbuild
33.6 KB
sha256:d0df4e9e1c49f58c9111dc033d58958c3181c4dbe898b1168ca27bdc7f0193b8
SocketDev~socket-patch~IRSP9W.dockerbuild
23.9 KB
sha256:d4f0944b31120d37d057f01fcec44c7bc793a6f2dd62cb3cec8402f537016dca
SocketDev~socket-patch~J69R6C.dockerbuild
33.7 KB
sha256:2978fc2707c4e6089505ba3b00c3323e3ac0e3b2a4529d9a8e71ff3024d1a09a
SocketDev~socket-patch~K5370A.dockerbuild
21.4 KB
sha256:7530c85066f02c7d34a3cd926e5417249624c2c9d69f85dbceebc997cdcc3606
SocketDev~socket-patch~KACW0U.dockerbuild
34.6 KB
sha256:8fbe990afeaec60bcd4bbc52d5f6ad509308ac462ea1fa687b6c67b75b3d9613
SocketDev~socket-patch~L9YW3F.dockerbuild
33.9 KB
sha256:23441c70b253afebf8944327b4eb4617fd8a000632e91ca33903582d16b5a3f7
SocketDev~socket-patch~LIIA1O.dockerbuild
22.2 KB
sha256:e5a9e944c61a5db55b3e5ed38734f271b269a5c25b54c478884d69c00160e057
SocketDev~socket-patch~LU9Z5V.dockerbuild
34.2 KB
sha256:983d27858e5c2643e5659d45f4117429fdc274725fe8663e6873e8f1e93dd394
SocketDev~socket-patch~LWGG7Y.dockerbuild
21.3 KB
sha256:d890d9011e71ad609742a40f589766846ea26d4e17c385b01cc50406538f3d71
SocketDev~socket-patch~N6H2XD.dockerbuild
11.6 KB
sha256:63d42d99f2b219204e94c168461de3d43d739c5155e488721bec5d99fde9e481
SocketDev~socket-patch~NAYWOC.dockerbuild
18.6 KB
sha256:4a1a8a73ad01c754eca41d8198605ec4f2160d920de2dc6edb7bdf404329a541
SocketDev~socket-patch~NLNBXI.dockerbuild
17.5 KB
sha256:962607d1fcd1a06c9bb022ad5a5870f89db89b39570bf1bdc33f481bef604264
SocketDev~socket-patch~OE3FL2.dockerbuild
21.3 KB
sha256:2e165d989707b358e30a923e187d812a729ab88cb840d4bf930b1f53e60a353a
SocketDev~socket-patch~PRXBA8.dockerbuild
33.8 KB
sha256:e9b3cd8ccdc6a55cb5764f21b78757583fc41d000aea76b3d6502564f35809d7
SocketDev~socket-patch~PWY437.dockerbuild
11.8 KB
sha256:4bbe8d37b8a7367de07df6f719a5b82cd98ab31a7398b6f30810447094a10b0b
SocketDev~socket-patch~Q3NHYG.dockerbuild
18.9 KB
sha256:2021f3981ca9c48f846cd877f51272e69af20d8f47010974c448896643bf0297
SocketDev~socket-patch~QNB71S.dockerbuild
22.7 KB
sha256:300778e43bfaadeb97ef6c97e267fee5dba9c98a71be96b287b8c21a82bb1852
SocketDev~socket-patch~QZ52C1.dockerbuild
19.7 KB
sha256:49f7afc07798bd2378414bcc0cc864f488c6026f3cb1297a327406136852bbdc
SocketDev~socket-patch~RGUSKF.dockerbuild
24 KB
sha256:3497114ae2d1331b3a0d90cdbc4dc37e2908eb022cc317abd764837dcbaa5f0a
SocketDev~socket-patch~RITS1V.dockerbuild
34.1 KB
sha256:b998d5f23ef08e1d5cde510ca5c9f6188d7477de9fb7b0beb3312f67371da3db
SocketDev~socket-patch~T7L1GC.dockerbuild
19 KB
sha256:2c1d8fa318ac8be62dcae94bcf718acf434965ce266feae3017ac0d2147b3e9d
SocketDev~socket-patch~TSEOCP.dockerbuild
33.1 KB
sha256:3468186363cdaafc244bcd6b5d0f4c6a891f7c7ff67f8b4d024089a8ad6a61ce
SocketDev~socket-patch~U67LM1.dockerbuild
33.6 KB
sha256:ed6bd4c71c36c26df17fdbf756384f42646ec282069f922babe18626a9ae6aaa
SocketDev~socket-patch~UTE6ID.dockerbuild
9.27 KB
sha256:d87d67a6e0a3a59177fefb955b5e228846d206461daa37b0791a9774fec1b148
SocketDev~socket-patch~UZ77D8.dockerbuild
34.4 KB
sha256:cad45814293e246d9da6bf385a809ac5a9c5cf2fb0d247ebbdeac02087e2fcb8
SocketDev~socket-patch~V10J0S.dockerbuild
33.1 KB
sha256:47b6f52ecc223ca0008a013fb9541de85eff5b580dac7cacf186bbc22999ee28
SocketDev~socket-patch~WQ727T.dockerbuild
24.9 KB
sha256:0657fa8ed6d906f2a0711172abfce9035a477f8aadd582ee2e2996f845fb1fda
SocketDev~socket-patch~XHY0G8.dockerbuild
33.3 KB
sha256:f6b53e25144efba89de65754224e47d26736b74fa665f0586d442afde22d3480
SocketDev~socket-patch~XZG2ZA.dockerbuild
34 KB
sha256:344458e5fefce00979d0b4efb91ff132ff7e7932b1c39738733fcc6bb48c2fb5
SocketDev~socket-patch~Z349F9.dockerbuild
15.9 KB
sha256:e5b3f32f62da23820ef966e75344986eb375e20764b9c7127c2df798b39ec711
coverage-docker-composer
37.8 KB
sha256:7c8f8d0e52192d92edba714df594a0aa00e1028ad99f4b7e24412391b5da1ee4
coverage-docker-deno
37.8 KB
sha256:dc775e4b2395c22acdd0310886bb3ecfd11e38aff1df201c1d64cef812fa07a1
coverage-docker-gem
37.8 KB
sha256:a979f4d8b89f3dbbac6fdef62c90fbfaba476d6bb8a5d232bb890d20b6d8647d
coverage-docker-golang
37.8 KB
sha256:6f12a20852fe9faa0f4b1ff94f047a5963e15a8c37d9b0bead051fbedb3fe285
coverage-docker-maven
37.8 KB
sha256:0d76b81336c8a7bd8963cdf5a803b9e58dea9e8433886033184166bc0009fba1
coverage-docker-npm
37.8 KB
sha256:902c894272b016dd061ae791f2be3fcca0a0145af85e290e8b4d5eba23f90a2d
coverage-docker-nuget
37.8 KB
sha256:50ae4d556761ab13e5a22db0e43940b2f88a9aa7a06497dabf5f28625f16559f
coverage-docker-pypi
37.8 KB
sha256:24ad75415b5790f3a2fff3f858662d8d5733a6e0a745be708a74a79ac6f47855
coverage-host
175 KB
sha256:5ae19374fd3e158a66179a0b44171527efb57d7831c025f3bb87413276f99382
setup-matrix-cargo
928 Bytes
sha256:93b70acdfae0f54db8fb0bbc74576cda0d78e6ff0d44d349ae1dec7a7e821276
setup-matrix-composer
916 Bytes
sha256:32313db7763e7a72c73231aad0e82543fc6a286b0d34498eab7da944aee3bc25
setup-matrix-deno
905 Bytes
sha256:c8c951e9ee501b709ce84aa72d71db07b27a504d3bec2c0036e35650175474f6
setup-matrix-gem
918 Bytes
sha256:88e5e59677197abcabb592a9b3cd8263088b8c1b8961f8c9b9f5b2c30503b999
setup-matrix-golang
911 Bytes
sha256:196ec21db0859dcad96317b59f09c87484dcccd823d3eeca49691530138141be
setup-matrix-maven
914 Bytes
sha256:a1a650248b374c4e9cedb36be9cae7a90a9bc4d344dc75fbdcc04ad9535ce15e
setup-matrix-npm
1.75 KB
sha256:1e67fb4350949c61025763dec4bfb9a943f29a40a81fb10e9bda084ee8289e92
setup-matrix-nuget
907 Bytes
sha256:3e71ad9e9f97b7bb80c403dfef7b7c13cb6834273f516241a026bc890fca8bac
setup-matrix-pypi
1.86 KB
sha256:2c59fd103afc0a71b351a971d00b1877ca9582bbfbce4f6d68c08b14aaede7f6