Skip to content

feat(api): batch patch lookups through the public proxy in scan #308

feat(api): batch patch lookups through the public proxy in scan

feat(api): batch patch lookups through the public proxy in scan #308

Triggered via pull request June 9, 2026 19:32
Status Failure
Total duration 21m 55s
Artifacts 72

ci.yml

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

Annotations

2 errors, 37 warnings, and 3 notices
e2e-docker (deno)
Process completed with exit code 101.
coverage-docker (deno)
Process completed with exit code 101.
dispatch-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (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 (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 (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/
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 (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 (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 (composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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 (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 (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 (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_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_coexist)
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_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, guard_build_integration)
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_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 (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_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~2IU0N1.dockerbuild
20.6 KB
sha256:babcf3f486f1d8a47e1c1a1a794ac1436f0b6e60b70af88a118ff7c9a780a5d9
SocketDev~socket-patch~2SFQQU.dockerbuild
33.4 KB
sha256:30a649ae58442db7426f0680b67c6221aea96dbf5b64dc2a700c436ed8a9206b
SocketDev~socket-patch~36T0MM.dockerbuild
21.7 KB
sha256:4b5676abfc0d842bd30b853c1c3e657b135f0a6da20909b9bf7ada45c1bbbe81
SocketDev~socket-patch~4TUX6V.dockerbuild
11.3 KB
sha256:3c160fc46422d85082a98eab567b4559cb66ed1416bd88e6fc5dec87fc22a4df
SocketDev~socket-patch~6MIPTW.dockerbuild
20.1 KB
sha256:b4d632868a3af0bed3060e7bc8daa22673e931ea0a0621e8a06b11ff7a6c6b3d
SocketDev~socket-patch~6MU8HX.dockerbuild
20.4 KB
sha256:6aecef3361ef29d7b828691551107b80dba9e0cdf235ce6594c3963fcad70ee1
SocketDev~socket-patch~6T6391.dockerbuild
10.8 KB
sha256:f4c31e45aa888044c5abbf37718c47f95702cdae120a4707775da47b278c0125
SocketDev~socket-patch~726IE8.dockerbuild
18 KB
sha256:79d8b9909b0fbdada5d2fe7787d355de13965a13885d089982ea610917578b44
SocketDev~socket-patch~77Z0DE.dockerbuild
23.1 KB
sha256:11c1fe7ddc665ee75312aa1d8806e807af8c7cd141c0cd10cad88355f9ce139d
SocketDev~socket-patch~CK29VT.dockerbuild
33.8 KB
sha256:7216ef506117923f5028332bd4428502bd2d591a66f82306f6f397e8a086f1f0
SocketDev~socket-patch~CREPE8.dockerbuild
11.7 KB
sha256:ddaa64e6e2894ad60d7ac8a30d515438c9fc5af54d0a14668ef9d45e9223cd6a
SocketDev~socket-patch~DMDXN0.dockerbuild
34 KB
sha256:0f3bb401927b4846bd97138e8d9f8b7c31a300699d5d12eff12c1cdf91f4a378
SocketDev~socket-patch~EYX40B.dockerbuild
23.6 KB
sha256:49386a9d2046637ee2cff8e2da69fbb9dfa0202ef0fa0884417cc3282ef3c91c
SocketDev~socket-patch~FD7X1X.dockerbuild
21.4 KB
sha256:ef5a1b802d788e284cd2657a266247eaa242cd711aede8915d3cb09afef4f375
SocketDev~socket-patch~I96UJ2.dockerbuild
17.7 KB
sha256:f67ad82bdf9f9f88589d38e4c2950c3248b6a3ec9ea7aa0b6e16ceca8ef39214
SocketDev~socket-patch~J1R6Y2.dockerbuild
33.6 KB
sha256:1f3fd252973841f36f4cd40b24795c94cd6a440f67da919bf6154882e2533c79
SocketDev~socket-patch~J4ONZV.dockerbuild
21.7 KB
sha256:fd1ce98c41a80358278394a438f0e1246f21f956264bca29e789f25c84858d52
SocketDev~socket-patch~JAKVQK.dockerbuild
22.1 KB
sha256:9ff2b08a6440c66e919d0cf79ef0d9d7f01c0289bbc9fbaa5ecf74c84c1f3ac5
SocketDev~socket-patch~JUY22U.dockerbuild
21 KB
sha256:3d1eaa1f9f2d02f92ce1c5c23aeeb2e7f64687e005379b9e99529cfe4fc49a61
SocketDev~socket-patch~KBS8MX.dockerbuild
33.2 KB
sha256:d296f84069e457a5ab37070576e7436766a86f457e618ec70acce46ae6f09d9d
SocketDev~socket-patch~KD1145.dockerbuild
18.4 KB
sha256:6f55188b539153886891eb427f548a30b0a3935df580f983655bedc89b85a1e5
SocketDev~socket-patch~KE9AIK.dockerbuild
21.2 KB
sha256:91f860ba15792c3fc4adb901162ca06e7fb249ffec476a9d12050e0a4564727a
SocketDev~socket-patch~KFO6QO.dockerbuild
34.1 KB
sha256:5a299757a81f94107c13b2b3b8bab75bfb74e9e803febfff047e0e590843a500
SocketDev~socket-patch~KWDRTB.dockerbuild
34.5 KB
sha256:4c270b0b7c8f9429953880d28b9035e0bd1be28e2324c0dfb75a368b286b4773
SocketDev~socket-patch~L118BN.dockerbuild
21.9 KB
sha256:fd5ce2d45491c2e767153525003fa73dea737e91944a9e301e4573dc0c5023d5
SocketDev~socket-patch~L48RGV.dockerbuild
33.9 KB
sha256:38dcab86d04410c2fbc38cd8da84d01309f3b947b235bb03c06093b76b633579
SocketDev~socket-patch~L7ZH02.dockerbuild
33.7 KB
sha256:9366c8fce105b1f11e9260254d34328790c80b5aaae31f5e50db38bc706fdea9
SocketDev~socket-patch~LCW2YL.dockerbuild
34.3 KB
sha256:d5c8a5495e39591b0ec0635282f36b22bea865cf642c246750d6bfd1f368aeb3
SocketDev~socket-patch~M0I5BX.dockerbuild
33.9 KB
sha256:c1b07a96fc1a6d74099a7102bd7a13232a5ddae321b32f5aec22c5c840c23a0a
SocketDev~socket-patch~NG9H1T.dockerbuild
34.2 KB
sha256:43b1da883faa69cfd369d2644f9f90200c3b07bb95c8cafd82b9aba76aee9a6c
SocketDev~socket-patch~NHDQ0Z.dockerbuild
33.4 KB
sha256:1d265d3aa32f635c0401e0aedbcd1970212532ca61c17b6e3f39b7160068cf33
SocketDev~socket-patch~NJKZF1.dockerbuild
24.1 KB
sha256:09be77f31a3af1b2668c8a406c60f7cfcfd017877ef80f6979cf7f356a55589c
SocketDev~socket-patch~NKN04P.dockerbuild
34 KB
sha256:091732813b5ad69a1e5db4f833b048cd96e98c4631ed7318bb4d2e37a94e371b
SocketDev~socket-patch~P3OKXO.dockerbuild
16.6 KB
sha256:beb6cbd5d3b893bde0829109bd576f05019d8624b737f8c2bff5ed6178367e51
SocketDev~socket-patch~PRKLHX.dockerbuild
34.5 KB
sha256:95b5229c9321d5ff5e09b77c8b31453140d7813f4d2755e64bbf986d19dbdf51
SocketDev~socket-patch~Q55Y8Z.dockerbuild
34.5 KB
sha256:d9d79c37237b826a96a24400d2b16f9909953792b877d8bb039155af5a0a1ef7
SocketDev~socket-patch~RB7JJW.dockerbuild
18.5 KB
sha256:40237cdedc8f80364de5088e3aade45d311d572592ffe17f562cb61b47993d0d
SocketDev~socket-patch~RS6CU8.dockerbuild
34.4 KB
sha256:770d5e534e13688857a4948a0e863cc1df5b283346e995b1ca7219796c92817d
SocketDev~socket-patch~RXYQAD.dockerbuild
34.2 KB
sha256:556d44024e4eee6dabf7e97ee81ba61a536cfaa152148a33b04a0de42e3177b9
SocketDev~socket-patch~S707YA.dockerbuild
33.6 KB
sha256:b407339df9cc9203f5f8b36addef60b39f0519b7155269630848f0fe30819ae9
SocketDev~socket-patch~SF52R8.dockerbuild
34.9 KB
sha256:197a7a77e193471ac398ce5a10bc66121bf33ddf68c5ecac485401c1bfa5e8f8
SocketDev~socket-patch~VDT0D5.dockerbuild
22.5 KB
sha256:50e443d41c15679db6da9aade77927e17dd211917b8df51cc205c853244d533e
SocketDev~socket-patch~VTOZID.dockerbuild
34.5 KB
sha256:d192f5a7223f1a704e7c8fcf0cc99186c459d753c8dd8d0ba1aeabf98a9c9f67
SocketDev~socket-patch~W6QPEI.dockerbuild
33.3 KB
sha256:a4eb7c9c9b41a5428205d58e58832d12673b4d86905f4464e8e48a0554d5e707
SocketDev~socket-patch~W8ZLNU.dockerbuild
33.4 KB
sha256:4a01850fa7239b92429d2fbc659fc0418f09073cfc72610f92148068dc4fc298
SocketDev~socket-patch~X6NT0D.dockerbuild
33.7 KB
sha256:7731e09191d2a20a647effac96c10b7ea6f5cadc844ec01c5cbcbf48d0fcc810
SocketDev~socket-patch~XAAQ5K.dockerbuild
17.2 KB
sha256:073775281f765066907376f9862a2bf0ddcae5d1922c2c03ff5c22101626f2d4
SocketDev~socket-patch~XEVHNM.dockerbuild
34.8 KB
sha256:c6972ec482c6fc545d549b92f6a45a8ae24bfe912a3f3923af8246d44213da5d
SocketDev~socket-patch~XHFD0B.dockerbuild
24 KB
sha256:bbf9c5109f95a1adf825dc8a35211b3b6f6610863373295f7f987afbc03aaca4
SocketDev~socket-patch~XJ9QD6.dockerbuild
20.5 KB
sha256:e6024ac38ad6c55d2f51b245f5daa97b46d99dff8ca2afd1c22546574b2b502b
SocketDev~socket-patch~Y36IJJ.dockerbuild
33.6 KB
sha256:897d740b7eef09a3a1c8f580e990a5e4439258b649cb80cecffc80319e9906e7
SocketDev~socket-patch~Y4GTP7.dockerbuild
23.6 KB
sha256:86c9d4790da168d2ba129f5580d116bcef77852e175d346676215202fdd99e4f
SocketDev~socket-patch~YNI53E.dockerbuild
34.7 KB
sha256:ea8db4e93fd16895a68e59f19884f8ebbc42e0dd6437dd9152c85b12b403d0ef
SocketDev~socket-patch~Z1VZ9I.dockerbuild
23.8 KB
sha256:dde10ccd924dbee5a0b3d30f97417448d102d032e407f1d0e756d039bb50d93a
coverage-docker-cargo
52.7 KB
sha256:ad32ab559a0e272faef698e124e0ac66d4ace893de6467a0a151c4473b960530
coverage-docker-composer
52.7 KB
sha256:27d84ddc4596228a1c2a9f22907dcb2eb35fdb04927d085951833a6f86acc335
coverage-docker-gem
52.7 KB
sha256:6e09e099cd3f6caad21327d3b599e6922342b6669dbed858bf5eb031bb200806
coverage-docker-golang
52.7 KB
sha256:df632513787cd6b4e89e9cd298a45a627ad707de454c02cdc2e717819f3d7775
coverage-docker-maven
52.7 KB
sha256:1dca14f11c6ce400628086c71fcd79f23ae73603b9c8db5b15866bc96c9f884f
coverage-docker-npm
52.7 KB
sha256:bfece0c8f3103df463d844b5f526f65fe75693169777ff71e5426eee7f9c741a
coverage-docker-nuget
52.7 KB
sha256:a44e4fbae0ca4b431a558f08398c618141c109fa23b5953d3c93310d141ad7cf
coverage-docker-pypi
52.7 KB
sha256:be324dc373e3ea0b8a86c11866122edd2ac3be80b1fc2341f6a09f3a5e878236
coverage-host
191 KB
sha256:57ea9f470192a6c09678452857281481b490e21af350bb96d684057499add75c
setup-matrix-cargo
933 Bytes
sha256:dccee4ae541f08360caa2c8d8218ba0aadda8e5a8dd2bc00d9440d325a8b7742
setup-matrix-composer
914 Bytes
sha256:301fd028b4dd66a4349fcdf7ca2eadcc4344d3de7aae8ab04ed21c074cb515fd
setup-matrix-deno
905 Bytes
sha256:6460d5d09a06001285eaee8a7de6e170908bbcbb0aa1726ee08266c4e3934a96
setup-matrix-gem
920 Bytes
sha256:7e88790e6c5b919871dbdacef82e6992db05a8bf3867e902f815e615c195504c
setup-matrix-golang
911 Bytes
sha256:1586aa873c190fbd04cbf03e4c85e0713e5d34a9f6cd27cb3769c7c77a97ba0d
setup-matrix-maven
918 Bytes
sha256:a6f1172b362fd057b0d3e3967185b80fe97bd7e852574673c1afa8333e2ffe39
setup-matrix-npm
1.76 KB
sha256:15fef64935907a0d791d8b44049b1bd700699a8089e6f391d4c8f0d99072b9c0
setup-matrix-nuget
915 Bytes
sha256:238c3be0ae1f5c9a3221699d19f698a1155a005176557a8a265fc9f6f6e00e13
setup-matrix-pypi
1.88 KB
sha256:b81eef6d73f49c0c26b391a1a75746a1ad2c594aa2402e75af85df0eeaf540a6