Skip to content

feat: vendor/scan/apply overhaul — lockfile-driven discovery, verified auto-fetch, mismatch-tolerant apply #327

feat: vendor/scan/apply overhaul — lockfile-driven discovery, verified auto-fetch, mismatch-tolerant apply

feat: vendor/scan/apply overhaul — lockfile-driven discovery, verified auto-fetch, mismatch-tolerant apply #327

Triggered via pull request June 12, 2026 05:00
Status Failure
Total duration 17m 30s
Artifacts 68

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

10 errors, 31 warnings, and 3 notices
e2e-docker (composer)
Process completed with exit code 101.
e2e-docker (nuget)
Process completed with exit code 101.
e2e-docker (golang)
Process completed with exit code 101.
e2e-docker (cargo)
Process completed with exit code 101.
e2e-docker (maven)
Process completed with exit code 101.
coverage-docker (golang)
Process completed with exit code 101.
coverage-docker (composer)
Process completed with exit code 101.
coverage-docker (nuget)
Process completed with exit code 101.
coverage-docker (cargo)
Process completed with exit code 101.
coverage-docker (maven)
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 (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 (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 (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 (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/
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/
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 (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 (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 (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 (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
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 (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_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_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 (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 (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 (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_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_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-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
e2e (windows-latest, e2e_safety_cargo_build)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
e2e (windows-latest, e2e_safety_pnpm)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
SocketDev~socket-patch~1PMI8Z.dockerbuild
34.5 KB
sha256:d24e267e545a12d52349965bce6c1910d1d919fac5b0e101c1f14a79c902d7e6
SocketDev~socket-patch~20OB2Q.dockerbuild
21.2 KB
sha256:fc7e71c26a4eb1c70709e5a86771ca757f52bed134c10353d0b4ba2de2dd36ea
SocketDev~socket-patch~2OL5DF.dockerbuild
11 KB
sha256:d6c6283fd07dbbe0873d1d602e19146c296c36a6370f4f0227e90e7609265428
SocketDev~socket-patch~2PZUSJ.dockerbuild
34.2 KB
sha256:cf87e48e44f85ab61265eb29bac93a4f745fa9ae70a5e4a1a3bc5f615b64c04d
SocketDev~socket-patch~3VZCF9.dockerbuild
21.8 KB
sha256:c733da0ead37e5a1dd623bb0fb688f95f30eb94f1e46a299367cad2d8fa6cc87
SocketDev~socket-patch~7ZEP4I.dockerbuild
17.7 KB
sha256:8ff7343de2185bb84e5eb1aae0749ccc340182c341a652ac32c7e8833a188524
SocketDev~socket-patch~8FYWGX.dockerbuild
30.7 KB
sha256:58e19245d8f4b0a8946b1bf879d5a69179f4190ededc73ca9271f3ae2865081e
SocketDev~socket-patch~8RGT5C.dockerbuild
17.4 KB
sha256:d79dbd4b585cadf6a8b7f078961af4a4fc057e4675da8e6b39aabc2bd488f6cf
SocketDev~socket-patch~9QNTMU.dockerbuild
34.4 KB
sha256:b6d76f6b262a06398a3abea8de065b0968f1514a141c414c49c8c7bcb591b3c0
SocketDev~socket-patch~C41DEO.dockerbuild
35.3 KB
sha256:d4f22e96f805a594eecf1a6158ad503e07a70880e5f49618ab4cc4091255e1dd
SocketDev~socket-patch~CKF9E3.dockerbuild
35.4 KB
sha256:8f91851acf81bb9f65d6520692ec58b9e3a1c76163ca3c89a40ab1f945598c17
SocketDev~socket-patch~D4WYIV.dockerbuild
18.2 KB
sha256:37be0e22d166fa2fe4876f5ccc2ca03105065ba2a86512f02d6001231314c947
SocketDev~socket-patch~DESN3K.dockerbuild
34.9 KB
sha256:5c69236a08687a196f200d88128c3d4a45eefa735e1668b247b45490786fef82
SocketDev~socket-patch~E76P4M.dockerbuild
34.6 KB
sha256:c1073c715797b2db08a45eb6b599017a5c96333a707f6f0afe601907271f39e3
SocketDev~socket-patch~EL3LWY.dockerbuild
17.9 KB
sha256:2db1f29b49fb2b4ac9c60080cad4ebbb96a6ed08201f5abef3deae171d009e77
SocketDev~socket-patch~EP2NT7.dockerbuild
21.5 KB
sha256:24007998a97e16396cb50e7c64351a40ca9d164ce9c4b5feb092ef0853cd81cf
SocketDev~socket-patch~G8SUDY.dockerbuild
34.5 KB
sha256:513594f9c6297279797039f6527c176dbbe31280dac462b2a5dd2035619a94f8
SocketDev~socket-patch~GRXF72.dockerbuild
23.4 KB
sha256:4a6ba8c318a6397072cf3bb8a4dfd24791e4f57f2f25652df3aa5b1b0397d2ee
SocketDev~socket-patch~IX9UDQ.dockerbuild
35.1 KB
sha256:a3898832f45d8fd32026a2a71b5aeb5c530553e909bae7a25a848b39b854f2cf
SocketDev~socket-patch~IYDSBW.dockerbuild
22.1 KB
sha256:86e43e4fb10a4a209fb4adb0f87b304228c89b019de4625d077ec3e10a412a1b
SocketDev~socket-patch~JKMHH3.dockerbuild
34.9 KB
sha256:36673284e6550d93f64ceb469bf00225b40293bc348f6e341f63c116113a8ddd
SocketDev~socket-patch~K2ZXE4.dockerbuild
25.5 KB
sha256:24e8a85284e14f5980e1bc7027aac3773d13bbe79e090134a160eb0781468686
SocketDev~socket-patch~LB4LJP.dockerbuild
34.9 KB
sha256:22b931bb898eb072bdd3feac508f1d0633c4cca7a12082755346fb268b18764b
SocketDev~socket-patch~LZ7OHR.dockerbuild
30.4 KB
sha256:aa945eebffa8fd7691788072dd4917988bd5100bed7baf9476cdd2e62867dfff
SocketDev~socket-patch~M0FNQM.dockerbuild
35.3 KB
sha256:05852d387fa69be3eb37a881338af3d3c67f8b41579857b61873d1e2ba56e77f
SocketDev~socket-patch~M6LX86.dockerbuild
34.6 KB
sha256:f58e0d11032a7fc77b9121183b7374fb366b91960734d9ea1cb340535a4fe2e8
SocketDev~socket-patch~MGYW61.dockerbuild
34.5 KB
sha256:2c0327295bb5c8954661f07562907c0f6f1e50f295480c20a3e9a17a99c0fb4a
SocketDev~socket-patch~MHRLHQ.dockerbuild
34.8 KB
sha256:30fd9a65d211bb2f6b124204921d3cefe15105232217f1330530e0377b71b6ed
SocketDev~socket-patch~MOCDU8.dockerbuild
21.1 KB
sha256:1454871abf74882db0ba8d9bb2f7fe00b774d6103f7a81eb110837561f8e41d7
SocketDev~socket-patch~MVYIBR.dockerbuild
17.8 KB
sha256:bd09368c6ee5310d91645d7bd1427a623db8830ab68ce376a143f1929b6fee5e
SocketDev~socket-patch~MXKSY1.dockerbuild
35.6 KB
sha256:6d56b1200d9c733ddf8f8e4f922d10c3e6a09f8a1299aeb16b992395abb3ce1b
SocketDev~socket-patch~OL2ZYP.dockerbuild
11 KB
sha256:73f9ba94a6ace0632f9f58d1637501ad3c903d78de035eacf8862a1b2fb84090
SocketDev~socket-patch~PTX9VP.dockerbuild
20.9 KB
sha256:d255e74b37304079b106a967e469fc9ab3db6bda145c0eae4b5ffd6e1ee72c69
SocketDev~socket-patch~R23QP0.dockerbuild
24.7 KB
sha256:063414d0cb25ca7b5909f2229bd8919bc1701000111dd32cc22296556ef3bc0e
SocketDev~socket-patch~REXC41.dockerbuild
20.8 KB
sha256:559cd8916ea525a5c695fd7c97cb7cf44c1eb35f5b549856477003848c944aed
SocketDev~socket-patch~RH1Y4I.dockerbuild
35.8 KB
sha256:bfbb98a96828cbfc81bead4f2a77006d425d73eb01d16e18822bf8a0860580e9
SocketDev~socket-patch~RXZ36Y.dockerbuild
34.8 KB
sha256:06459b4a05b74f68062c5d49bfcd6f00f9a037652e78c569dac192bfd39abb66
SocketDev~socket-patch~S8B9VI.dockerbuild
21.5 KB
sha256:43c5ee24923739a2ee893a2f2c27b0592526ea758cade7e3b157bc456eca2b8d
SocketDev~socket-patch~T727C3.dockerbuild
16.4 KB
sha256:515d898654813c75ead06a9507627ba81406e9a1dee26c4f0b78600ee3646639
SocketDev~socket-patch~TFX5N3.dockerbuild
23.8 KB
sha256:dec5f5d4856238fb99bcc711010639e9d912658e56c4fb8505f2657448f8021a
SocketDev~socket-patch~TJFXV2.dockerbuild
34.5 KB
sha256:2ab1af8c3bc72dc4ad1690447c22abdf3bc5569842bd23b083ad195b431a899e
SocketDev~socket-patch~TRAKQS.dockerbuild
24.3 KB
sha256:c0309a67135902f997b0a1bee9bb8a9f80add90ba607bb1a33aa45d8ca479a54
SocketDev~socket-patch~UNEWJV.dockerbuild
30.9 KB
sha256:1d79e37bbc0b9dcca196310a63cb1fa5b29cec4e20dcd9c2783dddb6a4fa3db4
SocketDev~socket-patch~V3OS3Y.dockerbuild
34.7 KB
sha256:cbd265ae788826c2ab35433d14a03fb02d9c64edfe8ffc8132864b276d2a7250
SocketDev~socket-patch~V5VTGQ.dockerbuild
11.1 KB
sha256:2c922bb5b3584c99d8b3a4f4f3428185587d303d660e4e33722f6ecd1c13add0
SocketDev~socket-patch~WQ6SN2.dockerbuild
35.4 KB
sha256:b01b29ea7389b620ba2976e9db67529d207853008580a745a1e46589b1d13aa5
SocketDev~socket-patch~WZ3NIR.dockerbuild
34.7 KB
sha256:adc84ee2d2b613e6ec1458fd4c06ded6c475d052a7c389e439612839b993fbbe
SocketDev~socket-patch~XIWJG4.dockerbuild
34.1 KB
sha256:f55438eea5e8f2827bb68ee280de30cbb9141989b344f4018bebc94ba2aa083b
SocketDev~socket-patch~Y48XR6.dockerbuild
25 KB
sha256:9909e5baeb7b6f3f40c08abbfcfdc168b8faa60ed9180149b6f3d18e9417126a
SocketDev~socket-patch~YBVVZQ.dockerbuild
34.7 KB
sha256:db17d6d50beca48534b88c1723f0d05af76c6e593c8b3f4d91e06f67871bc084
SocketDev~socket-patch~Z31DSO.dockerbuild
35.7 KB
sha256:b44a9b99f7143b5192ddbccbe1cff5b38443adeef1ce73475e99bb6459b11f0c
SocketDev~socket-patch~ZFQZR2.dockerbuild
33.6 KB
sha256:54a0b9e1880ad533f63f26d4ec6e54ab1bcaeb70f0c2ac30c4badab4cddf075c
SocketDev~socket-patch~ZP9WMO.dockerbuild
22 KB
sha256:ae7062eadfddb03c388f85313a27bd78f1a3a3ffa6faa2ffba8c9e7cbc04d04b
SocketDev~socket-patch~ZW3K1T.dockerbuild
35.1 KB
sha256:9fd9796405c17b7c5673d3e2725d925686724ca4fc354e032b7dda628c66fe7b
coverage-docker-deno
87.5 KB
sha256:b42dfbf7f5dd669bac23b3c47bb5cd9729a63c355f6a945812a765fb162f32a1
coverage-docker-gem
87.5 KB
sha256:7699468009399db743eeb9debae00a91802a90e64f2392300ead5a91f6cf8c44
coverage-docker-npm
87.5 KB
sha256:e5fed574643419caef99244997f16facbc891daf897558d82890d2721eabdf52
coverage-docker-pypi
87.5 KB
sha256:960a4429270929658aee44e2e30c13ddfa26f96232e581f2296a3c627ce99e13
coverage-host
302 KB
sha256:f3ac1c07236f2895d6be114b11458d6bfe1681f8387e0142247819915af80ad1
setup-matrix-cargo
929 Bytes
sha256:d441221c8a8c80a1d0417fdddfd70a650da567d3b5653842d42f2f39092eef21
setup-matrix-composer
922 Bytes
sha256:de944afe2ab9a6f79d3b490f076a5cc1443cfed8251ba7d5121863166e9de4a3
setup-matrix-deno
905 Bytes
sha256:961db1f2357ca4c07cd1c64ef02d9d6599684e97b51452a09e4d47c27d3c4cac
setup-matrix-gem
921 Bytes
sha256:cfcd285710eb8ae90171a838bb4b966ca6c630e9727fe4a8cb827afaa1e638df
setup-matrix-golang
911 Bytes
sha256:972f0a6a161c2d64fdc5d4f7b1c797b739dd496f27c9727bf2a54bdb1bd9b125
setup-matrix-maven
920 Bytes
sha256:cb0c6d54901c19df9a43b82e3618b747769e0fbec40ba63acf0b3f195e36009f
setup-matrix-npm
1.76 KB
sha256:204271e0203c6212fc242dd15581896fc063bd4baf7b29c0bf4ba6439e9e9463
setup-matrix-nuget
912 Bytes
sha256:6d5443908dbae742ca801eb7f576bdd7cccde4b2c37420a9951cf273b7f1a13f
setup-matrix-pypi
1.88 KB
sha256:0faf33a1062238dc55f803160cbfdc6524e7497ca811f4e2f1d4c1ec2501bcdb