Skip to content

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

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 #326

Triggered via pull request June 11, 2026 23:57
Status Failure
Total duration 28m 26s
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 (golang)
Process completed with exit code 101.
e2e-docker (nuget)
Process completed with exit code 101.
e2e-docker (composer)
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 (cargo)
Process completed with exit code 101.
coverage-docker (maven)
Process completed with exit code 101.
coverage-docker (nuget)
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 (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (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 (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/
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/
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-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 (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
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_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_composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_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~3UKILN.dockerbuild
24.6 KB
sha256:74f3334f0cd7d5fb5439f8245881746aa22959fc5265ae8090c5aa5ce6e08534
SocketDev~socket-patch~4HFAHE.dockerbuild
18.5 KB
sha256:7f978e04084cfb7fc8ed4b9fa8df867a93349e0eb5c29baa32f716a48affa199
SocketDev~socket-patch~7KXHA8.dockerbuild
34.3 KB
sha256:29a44ec0aedad9ff646beaadfb3be50cfd31c3c6af18f9edfc9465bd5b2d336e
SocketDev~socket-patch~7MWXVT.dockerbuild
20.9 KB
sha256:a7874870263dba35375a5199decfa0d02b49c38403ec46ce031b3dc56be09feb
SocketDev~socket-patch~8LO53A.dockerbuild
34.8 KB
sha256:8315d5e7c35c053b303f01a812152054cd942cec5478eaced8fbe072ba07bac2
SocketDev~socket-patch~8WUOPU.dockerbuild
18 KB
sha256:6c1eacfef65c0cce13c494137c4b8e7e612d6db8ced4a8b9ddc0359afc582a08
SocketDev~socket-patch~94373N.dockerbuild
22.1 KB
sha256:10b8fea3f6fa6aba5c5c850f8031d3f9d0dbc870a7d0bf8204b608c35845e811
SocketDev~socket-patch~98ZJMF.dockerbuild
17.1 KB
sha256:23bbe1709c798e3e82bb0f875173548b1c3cbb25c70f406ef2bcb7a6500c4bb5
SocketDev~socket-patch~A41MA0.dockerbuild
21.6 KB
sha256:fe2a33e6c895f38e50288c640a0cb67a50ca6e104e361826e99069a889e4fca4
SocketDev~socket-patch~CBNAX3.dockerbuild
18.5 KB
sha256:0364fdc8fa7abba8042294c89dced6f4ad73f369090b48bd0d72c5c87cfc5d71
SocketDev~socket-patch~F3HD49.dockerbuild
34.8 KB
sha256:0fb990b21b2ff9049b14082f66d2818527c95a61330f8d55d43522908e9342b0
SocketDev~socket-patch~HXK03O.dockerbuild
11.9 KB
sha256:d1a247c7dc08cd4411cff217148ee2995b63ce67bf94e1a2ba1d37c053e015a0
SocketDev~socket-patch~I3XJ3B.dockerbuild
34.3 KB
sha256:52170e7923d89ba5b49247547d11e6db37dc9b595295e56178431aa154125086
SocketDev~socket-patch~KQSIH7.dockerbuild
35.2 KB
sha256:75b30641ec3fe779d6723ba9918551abd39899d3e52e9db295b5df168f1046ce
SocketDev~socket-patch~KRU9RI.dockerbuild
21.4 KB
sha256:89b2a313280b2bffeed8beaf21826aa3f352cfb1144f669444107da0fb4e8240
SocketDev~socket-patch~M0SOC3.dockerbuild
35 KB
sha256:391befcc7bc29c79c0fde064c66f33985b62fc8ae682bfd2b29247578ca36352
SocketDev~socket-patch~MNXY3Z.dockerbuild
11.7 KB
sha256:c77bdf946f4c5be714ea6d37011f06fb38a3baef742f0c1f89007b11cc6a3017
SocketDev~socket-patch~MYA05L.dockerbuild
22 KB
sha256:cddb8d2d4dbbefd5e0e95c5c4c67a63472a45997bbef798db5021bceedb6d065
SocketDev~socket-patch~N75VHN.dockerbuild
35.2 KB
sha256:455f65caee155270a5c3afdb04755682f361e83d7bfb1855b31563482b993f85
SocketDev~socket-patch~NZJBE1.dockerbuild
23.2 KB
sha256:fa810964ddd23849131d617bc558cd1c14df9b3acea9859f91cf3d542d17aee9
SocketDev~socket-patch~O588BJ.dockerbuild
35.2 KB
sha256:930d322b0c60439ba4e73eecb0de77ab84eb1faf201b176926c06383dd6af5c8
SocketDev~socket-patch~O6QQIM.dockerbuild
18 KB
sha256:90dfb1b000781051016ee4bcb6579887ab6bb1c888bd9cfede555e8da024ca99
SocketDev~socket-patch~PD9D0G.dockerbuild
16.6 KB
sha256:77d83c91d27f69c96799fe9fc8a0116cbdb98914ffbb44ad46a84a3c169d2f76
SocketDev~socket-patch~Q9EBTV.dockerbuild
35.9 KB
sha256:77fe86d2bf39ed44dfe775a5e5f42502f620c6bec4b00da1c42cf78e358a768b
SocketDev~socket-patch~QAQBNJ.dockerbuild
28.9 KB
sha256:3ed1891e3cc9f714c2c9a1282074e35cd71e8059ea3e6dce4d7a29347449c6bf
SocketDev~socket-patch~QB5JGW.dockerbuild
34.6 KB
sha256:8be1abd02768e52e0ab9abec98d87a592dae568d1e68005d56a7e5e6117d2d82
SocketDev~socket-patch~QORRHU.dockerbuild
34.6 KB
sha256:f9cbc4fcb13ed28f0254274fdb4b3baf4e84a3c2ad4c27df030a7df96d527058
SocketDev~socket-patch~QT0T6O.dockerbuild
35.1 KB
sha256:60f8ae0c1e2b2d34a4c2a9e26e01e6f5d2beddd0f51742f75f906a83b89940c1
SocketDev~socket-patch~S0L2ZL.dockerbuild
24.1 KB
sha256:1dfe0da09b06bab24096f1fe6b4a826cf99a33c2cc46ba7799421093ac86befb
SocketDev~socket-patch~S86E6W.dockerbuild
35.5 KB
sha256:a0b3eedff721b0d8922b6d3b78909c48e65c0bed47ab2602487cc86c6b8c23fb
SocketDev~socket-patch~SCK5YA.dockerbuild
30.2 KB
sha256:aceb3edea42c7a0636d4cc7c4e865739461ab6293ee004df6f70f3d8bc87a109
SocketDev~socket-patch~T1EX9S.dockerbuild
35.3 KB
sha256:159efc3dbe99123db5fdac9aa93046752eda2cec8a59b9fbb491bbaa75064c41
SocketDev~socket-patch~T2LCQB.dockerbuild
21.7 KB
sha256:7b4e464802339727e08667b41725245365c9b73e986b0e1a3cd3f4c76d3c86dc
SocketDev~socket-patch~TQ8QDQ.dockerbuild
35.4 KB
sha256:3d25a6b7a2cf24f7f52bcb8233243eb2e2542a9f051870b8eede75c21166f5c3
SocketDev~socket-patch~TR8RN0.dockerbuild
34.6 KB
sha256:d13f459db10b7538949ccf8bb76f5786d80b886724b31cf4a8f59869a17741ff
SocketDev~socket-patch~UA6J9J.dockerbuild
25.3 KB
sha256:d5bdce42f18e4169fb38f6cc4aad0f10c138f2c970ceac1fa0414062570410cd
SocketDev~socket-patch~UW4BEY.dockerbuild
31 KB
sha256:ed03af6a1dbd244ca43de66a2a71e07b0b84913a6464795a9ec0f34848316349
SocketDev~socket-patch~UXJBGT.dockerbuild
35.5 KB
sha256:32c88caec2fcac8daf40989551e58c66c15389928dff3bfe8f57cae86203ade0
SocketDev~socket-patch~UY6L87.dockerbuild
35.2 KB
sha256:c782f3538d258c18b78f7b851a8d0f1c1f09c4abcabd4d6aa0806ee7b32303be
SocketDev~socket-patch~V3IPUD.dockerbuild
34.4 KB
sha256:c93eeede45cffdb4aa026af092eb6b2eaa9457c321df032bc8a83691df72eae1
SocketDev~socket-patch~V556YE.dockerbuild
20.7 KB
sha256:031a9ce81a3b57b76685914830987600db1fc8a219e491e09b801f2cafab6726
SocketDev~socket-patch~VNNQT6.dockerbuild
34 KB
sha256:a7f6fbef5946dc2250dec459782472c90aeebeb6f15c6199573b04bd1e9178c3
SocketDev~socket-patch~W8C8N1.dockerbuild
35 KB
sha256:b2a29cfb4e7922c75e1719cb4d1b1d2ca0f26af5f7ac2929679b3cd4dcf96672
SocketDev~socket-patch~WWA7KY.dockerbuild
24.3 KB
sha256:6464529a4d3ad81d6a3253e2bf13a0d9e1056231d763c07fc6bb4850f0c14ba2
SocketDev~socket-patch~X48Q2B.dockerbuild
35 KB
sha256:1bb274e24202de46c8e7420a04307736399ad08739b2d1d4a741c3d5e1c6fa0c
SocketDev~socket-patch~XBTGVS.dockerbuild
34.2 KB
sha256:3f23efdb556a6453224ec01860669095b42d9e9f1d6188d541af12c28318f233
SocketDev~socket-patch~XKGSPY.dockerbuild
34.4 KB
sha256:88d6e2489277e881a9115a5f3e2ac4b42dd9ca88ab5666d1b98c46cd9fd4b881
SocketDev~socket-patch~XKLC4Y.dockerbuild
20.9 KB
sha256:525ba60a810c50feb3359c1bb705383c24c781ccd76f2e3f8cf7a26b26906b43
SocketDev~socket-patch~XR274H.dockerbuild
35.6 KB
sha256:6ad975692b7c2f1dc424c7ed79d97ef93eddc908aa8a929d473c8f5135526a92
SocketDev~socket-patch~Y84R19.dockerbuild
11.4 KB
sha256:ccef1c5993337e3a795735c3c3e22c5593ec7149e705587c08a38a3708daa996
SocketDev~socket-patch~YK130M.dockerbuild
34.2 KB
sha256:6bd0bed36214c6820dbff0f2bb61eaa25fed75e94696e5738c220a7a73ab6551
SocketDev~socket-patch~Z2BNCD.dockerbuild
24.2 KB
sha256:fde0d4f9e0726bbb59d229337978c19ea746095337c347fd4f5b7a3308429ec5
SocketDev~socket-patch~Z6GQOW.dockerbuild
21.5 KB
sha256:175f520cdb7f626335d8cf8d48b710da5519c4b3d62e4bb3babe621984c112ab
SocketDev~socket-patch~ZUJS14.dockerbuild
34.7 KB
sha256:1fe92a27a5b973e162d8c49c77dd65c42ec5e9c0717dc8f30c59fbe6d004eafe
coverage-docker-deno
86.7 KB
sha256:456689635774478f83b969416209068ae7c3a827c705f062a3e93dca84f078a6
coverage-docker-gem
86.7 KB
sha256:b3af7b8dcfc5d9680832fc0425fdd499c49b230ad35820b0350bee837d9b2301
coverage-docker-npm
86.7 KB
sha256:0466c01cceb77c31ccf5395e7eddd06937ec8d8b519955181840e4c0d1c92bcb
coverage-docker-pypi
86.7 KB
sha256:fa6a6fa91666d5fbd798ff4589b1935c0660c243ba41a7fe1eb43b6a08ff2eca
coverage-host
300 KB
sha256:e95d6d59c91361c682a0c42efbccceb76a2f2a00c521c7cc5868e7de2ce8d346
setup-matrix-cargo
927 Bytes
sha256:e77f3a8a3e631340ff2abe901f2173791eee286e20cd850a60b5d97202760dc6
setup-matrix-composer
916 Bytes
sha256:c13ae98553f6e5b37c6a7174eb34fc87674db2ad1e4d4947fba121e0d738cc16
setup-matrix-deno
902 Bytes
sha256:dd935105ca0991f728e206b86d81fe02a170105844a88212aac474ac74886571
setup-matrix-gem
921 Bytes
sha256:27aca41b4f92ca5d153fe6eab1d8719e2bf207803a8b075440af54b0412dce04
setup-matrix-golang
911 Bytes
sha256:35a32e46a9f71763d7af4980ef940affa3d233ebeff3303d62621f17e5c34e43
setup-matrix-maven
920 Bytes
sha256:8005121fbe2f0294a8abd95e8e0906422b3e1478ce525b5a67d3c8a021b3df3c
setup-matrix-npm
1.75 KB
sha256:c54a8a8f1396fd570aa764294e1d038da529103b048f15beff73c3632f8059fa
setup-matrix-nuget
916 Bytes
sha256:9c4a09ec254e0b7a52b10a261043a5075b14fced6df11afa3e1c3df74a5b9d00
setup-matrix-pypi
1.88 KB
sha256:9c9b61aa67fd7c3b61048973f0c75233ffbeb829ed5ded6a40a566ccea48366e