Skip to content

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

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

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

Triggered via pull request June 3, 2026 01:27
Status Success
Total duration 10m 26s
Artifacts 72

ci.yml

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

Annotations

3 errors, 38 warnings, and 3 notices
setup-matrix (nuget)
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 54.158.241.65: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 (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 (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 (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 (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 (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
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 (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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 (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 (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 (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 (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 (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/
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/
coverage-merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, 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 (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_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_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/
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/
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_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_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 (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 (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 (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/
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/
test (windows-latest)
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
e2e (windows-latest, e2e_safety_cargo_build)
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~0T7UAN.dockerbuild
33.7 KB
sha256:08598527aa17736b461a3d26a109e92ec45a307a804593123fbc6ed7c9c98e5d
SocketDev~socket-patch~0YIRA5.dockerbuild
33.3 KB
sha256:b1afb40d911753893ea8ee813ada1f26acf44b156cbfa8c58e3ab359db6a7bf5
SocketDev~socket-patch~2O3SVY.dockerbuild
33.8 KB
sha256:1cc40a4ecae9658aaebcade46c328d9599235b5f885ba2edca9b5081d16d7051
SocketDev~socket-patch~65DAMM.dockerbuild
34 KB
sha256:61343a9c52446d52deefc8525b4d160414a5290839bd8d3c9172f2e7acddd291
SocketDev~socket-patch~6GDX9O.dockerbuild
34.5 KB
sha256:24b67442d12856a9bd6e3999b0b01dec98e687e6136e1047576136a331d12dbb
SocketDev~socket-patch~6NFIKL.dockerbuild
34.6 KB
sha256:67d2b1bab2aacd8c7506929f80d653d554e59ad16d8ceeed3b2cb0b1b04ee5b4
SocketDev~socket-patch~6OPSJY.dockerbuild
20.2 KB
sha256:a4fc952da5ac7e95aeb70bd8f4d63fb11e32dc964f0553930d5cc5aea4d7b8f9
SocketDev~socket-patch~AAA7BB.dockerbuild
34.4 KB
sha256:df1f4be428437b464381ab257f25c4ebc0de16d88fdae63837db2eeb91f1fc72
SocketDev~socket-patch~AQMAXO.dockerbuild
24.8 KB
sha256:5f296801577d8b746b72b90de918c40a513826cc9276a72bbdad2abec2dd05b2
SocketDev~socket-patch~B70S5L.dockerbuild
34.3 KB
sha256:2ffadd2b162563f468677241107b2f91d12e57c662395df256d0ab503a3ce10c
SocketDev~socket-patch~BDSO0N.dockerbuild
34.9 KB
sha256:836ddc0fe55f989429804e07c7a039722bb408f8e56c7c77b8ae8d2487a2f559
SocketDev~socket-patch~BL6892.dockerbuild
33.8 KB
sha256:98d01c9bd82845386281fd9e291b41bbb9cc13b8c072a3c9e04e9d9f9663b33f
SocketDev~socket-patch~DSUV8N.dockerbuild
34.1 KB
sha256:9a96b668413904eed5505b39756e63b5186fb933e1859f85602cbe4ee9ad8c0c
SocketDev~socket-patch~EUQLFS.dockerbuild
10.9 KB
sha256:b4d7fba34ec95819f7b94b9e8b1726997afbd0b7792c0240ee28d081fd2b2484
SocketDev~socket-patch~F2PN0O.dockerbuild
23.7 KB
sha256:f307d84b123f8f2a5805f25b60509bae3b22f022944e454c2bcabaea8a4446bd
SocketDev~socket-patch~FKWJNW.dockerbuild
33.4 KB
sha256:1450d8dd23c70b3e8ea1df74d3413a05fb9532df2930f2a168501df6ce6518b3
SocketDev~socket-patch~I2E5MJ.dockerbuild
34 KB
sha256:8c282293f458c5aa14e1c304877af920106e0d7aae5b8e1f3e30aba90d8b8a76
SocketDev~socket-patch~IOA2TO.dockerbuild
33.5 KB
sha256:7fda34ee4e99212d5488f812aeb44160be9d10dec18b27fd427a19e83e3a26bd
SocketDev~socket-patch~JPRTLQ.dockerbuild
33.5 KB
sha256:3dbdc73c75fafd21f3789e4076648f15b7073e7a461f1bf11ce7805ec185c7fa
SocketDev~socket-patch~KDM8IU.dockerbuild
18.4 KB
sha256:8dfa8f822facaa6886bdc99f9c1fe2cd1680a646d8038e43460daf38338b0786
SocketDev~socket-patch~KOSQ2R.dockerbuild
18.8 KB
sha256:eefe925b6be0fb43c20c85f00fdf744c4a1f5651e1092ab068d5cfd9225b6abb
SocketDev~socket-patch~KV60BL.dockerbuild
20 KB
sha256:f61ff59da18e1161c193b9069c08a79be8bfefa9c7db2965b43cb90316fba37f
SocketDev~socket-patch~L50UW5.dockerbuild
21.5 KB
sha256:b83e293b2139f25812d03bcb8c35f880f785afe203d32304455e2ac7310c0cdc
SocketDev~socket-patch~LLS9TS.dockerbuild
33.5 KB
sha256:46c02e6cf662a8dbbef4c3af0e720f98b311b6eb8682ae5ab19f357da6dff772
SocketDev~socket-patch~LRM1LX.dockerbuild
24 KB
sha256:d15b334d12969d040afc70bcbc4eb82aa9cc1d8dc128fc9ea82928bfff50dfb5
SocketDev~socket-patch~N0R0R9.dockerbuild
33.7 KB
sha256:8a56afdfa411de77deadd5da1f6ba67b0bafb54bed4e7570763dcdac3ccdc917
SocketDev~socket-patch~N5EMV2.dockerbuild
19.1 KB
sha256:901df2495c5b36e7fdff0ddd427425a4b93b36a25badb5fe6a8fd08e9096840f
SocketDev~socket-patch~NQJDEP.dockerbuild
33.3 KB
sha256:1d2a006250c287851901843d0faa1b9720df4468c354db021317250705085922
SocketDev~socket-patch~NUJH3P.dockerbuild
33.9 KB
sha256:bf77ae230f1d673570c4f579b8552c4575d1d1cc92d82adcf5cdf7eb5b4ab00d
SocketDev~socket-patch~OHHSY1.dockerbuild
33.3 KB
sha256:e39e9962003f7c23143fab5b989174e9a4ef6a14df83af59368bb7e3581adfd1
SocketDev~socket-patch~OTQE4Z.dockerbuild
21.8 KB
sha256:c2d1b513bfab04cf03098cabf42356aac9a9fc68c21214bfb70a21124b53a0cb
SocketDev~socket-patch~OUYAA9.dockerbuild
24 KB
sha256:c83eec4a58e2c9e86dde8780689fdaaaea6631f9d2eba4b319e481d7b0356f6d
SocketDev~socket-patch~P1PPI2.dockerbuild
20 KB
sha256:b4016fa59d1b7c9a75a1a25cc49ac86c2a4703b197f1ff999ce203edc5d750b9
SocketDev~socket-patch~PK8K71.dockerbuild
16.2 KB
sha256:ff3a701e3feec2e319f9adb8e17dbf524e895da57310695dfbc25ad33971a93f
SocketDev~socket-patch~PNDJRD.dockerbuild
22.1 KB
sha256:e6d484c970c140818918d035869dec4ef805513707fe11114948cec200bd3c02
SocketDev~socket-patch~PRE5DC.dockerbuild
34.2 KB
sha256:2b664b6628ae66a0e9f3fb68e7230383dabf4144d7b2bd6ad0b24b9251a70ae4
SocketDev~socket-patch~PX8AQT.dockerbuild
33.8 KB
sha256:b35847ff612701060dd5017262cac829c9481d9c816f6110040079cceeb28cbf
SocketDev~socket-patch~RLBJ6E.dockerbuild
33.8 KB
sha256:fcee0ca9f5fb63920f02fa3972f68cadf639c7b7c3f2e2028d1963b11550d1dd
SocketDev~socket-patch~RYUXBL.dockerbuild
11.7 KB
sha256:79c04ed2fdb6e21d218890d6ddc2daf0b600c9e493d5714345185fd0c59692be
SocketDev~socket-patch~S4IE0P.dockerbuild
21.4 KB
sha256:af6d21dc2d208c28042ce4402f9be4a724961048d36f7b27f771546df1149df2
SocketDev~socket-patch~S4UHTN.dockerbuild
23.9 KB
sha256:265091d929e57dd420d93eb57afa53270ceca1a0e7863e4a4803c38f2451afeb
SocketDev~socket-patch~TU3FDO.dockerbuild
20.2 KB
sha256:de4dd34cdafb53c12b1f97b145c5b769b43e622570dee95e9c376a48d38547c2
SocketDev~socket-patch~U1N9TP.dockerbuild
21.7 KB
sha256:1281d1af6d39063ef73ef143c5ca6fed51db1093ef2b8e411adcf8aa9bdce4fd
SocketDev~socket-patch~UXZSVN.dockerbuild
33.4 KB
sha256:74eb836ad8d518b123367234049502493858cb70207edfe115203ee53a0a1b76
SocketDev~socket-patch~W448LZ.dockerbuild
21.3 KB
sha256:f405803f7fc4e1bbbbbd3086d2da4884fc992e4e0c42c49881407bd077b8e5a5
SocketDev~socket-patch~WDU10T.dockerbuild
9.22 KB
sha256:83b2c71553a1ab638ae597fee98e541dda2d592c0f414f436c565a44eace083f
SocketDev~socket-patch~WYT1MP.dockerbuild
34.1 KB
sha256:a7f3305ed7ae838f762dbec08cd69c6ed2297ad1c8ec9454a323f76923af3b70
SocketDev~socket-patch~X4D71Z.dockerbuild
33.8 KB
sha256:450987841637eff5e55bcc9a1556048e811141b6336b5e01d9aaa1e1b3737520
SocketDev~socket-patch~X4JKWT.dockerbuild
22 KB
sha256:04b332a98e62ee1d209ed6816ba72db7d0951a3942521f668e688dc08567fefb
SocketDev~socket-patch~XKT2G1.dockerbuild
18.2 KB
sha256:ebd05794f04d532360ac2f0a2e2a028ae6ed06a32b9a2598c3209e79df19fa35
SocketDev~socket-patch~Z2BERY.dockerbuild
24.7 KB
sha256:8a681b169f017e10362918cdeeab4cee2476ccfbb73587afaba8947669acc295
SocketDev~socket-patch~ZCD1QL.dockerbuild
21 KB
sha256:e6d8221cef6b0f785369f1444b00d2cf5526e06b28704596fdfcb21f39788ed2
SocketDev~socket-patch~ZP7SJ6.dockerbuild
11 KB
sha256:cd159e53fe7e5b662173497f97e63fb2b3d47c9842b913d19ea213b44f07575a
coverage-docker-cargo
38 KB
sha256:399c63ba3e0f142fffd0269cae73330d4045772d85a23852b293a29c485387eb
coverage-docker-composer
38 KB
sha256:6e1c36505d58b8381412fd3faa07f59701a9fde442fdddf464cbf70d1c7148ee
coverage-docker-deno
38 KB
sha256:5f97ee1be8c3a928384560a318463c931ae69864d9753c2d6e866aad752aa459
coverage-docker-gem
38 KB
sha256:1745076598daddd9596d1d82556814682bdedd110659a7977dc069a319218340
coverage-docker-golang
38 KB
sha256:bd6aafd83a5a72440d20b5d829b0f356ac7f95c158769c25c9837baa804d6db1
coverage-docker-maven
38 KB
sha256:1029708b465f8db854e6bcaa7e456ff49c22c70136dce7267b69b984d37aa3b8
coverage-docker-npm
38 KB
sha256:edcb0675b322ef18a60bfc7db7bcd5579bfd51d74e8defde5601faf81f312fc6
coverage-docker-nuget
38 KB
sha256:94ae34a8427b514e042b0416c5a2bad316579eb540d0bf08aaaee0a67a416b71
coverage-docker-pypi
38 KB
sha256:b228bad64a3aec7b92436ea931e682b70dae216bdad457bd95598f4d138f0dd8
coverage-host
130 KB
sha256:265777eee8f5c59546c574bcd3f04c9d962a5d9c57a65bc34a6972f604bf24bc
coverage-lcov
136 KB
sha256:9698c04e166023e0facb9f7033136b9bf50b55344489e4406e588432a034e130
setup-matrix-cargo
926 Bytes
sha256:63c8f4e408ff121c574de1e23b09e08b90bc42c6d104927884d4898de87c98d0
setup-matrix-composer
921 Bytes
sha256:0518e02711ed621c1ceda52a974c38d3d39bd24146da2cb20aab2f10e3221e74
setup-matrix-deno
909 Bytes
sha256:461692a7cf1629aed2e05e4cb3c4a34f3f5c6edafb4d75ad53e09393bc48c7b9
setup-matrix-gem
918 Bytes
sha256:39a3e665e0e25a41f05530fdcce1e13a9a51cd550758a88aa962b0bf1c9a7ae4
setup-matrix-golang
905 Bytes
sha256:c0c889a3c116a6bd6f792a1e05757d8e0a15aacef82a63e6893c80eda054c43a
setup-matrix-maven
918 Bytes
sha256:cd2800d623bcedbb3b8e74543d7b1ca9da8b184f1a8a8e8c2142d509d263666e
setup-matrix-npm
1.74 KB
sha256:4b61acdc632edad25a7bfff8b181f507bc70704c416e1b0b6944a098d2831bd7
setup-matrix-pypi
1.88 KB
sha256:a51bcb97e59c8b25629c05df125bc98045be625926ae7a6e2a779008085c49fa