Skip to content

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

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

Triggered via pull request June 11, 2026 23:37
Status Failure
Total duration 24m 10s
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 (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 (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 (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 (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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/
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
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 (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 (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-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_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_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_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_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_pnpm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (windows-latest, e2e_safety_cargo_build)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
e2e (windows-latest, e2e_safety_pnpm)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
e2e (windows-latest, e2e_safety_cargo_build)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
SocketDev~socket-patch~13UPCT.dockerbuild
18.2 KB
sha256:34eb08aa8ddb4a0cd2f147e06a37e6a3a22697c911d48505dcc5236b706df526
SocketDev~socket-patch~1BO7OC.dockerbuild
34.8 KB
sha256:fb4f1e83530174293394138b6ffcecb9dadffbc12eddc6bc1ba035c20a76c17d
SocketDev~socket-patch~2LA88Z.dockerbuild
36 KB
sha256:19d384437d9572e0e50c52c4689fa65ecf5c7392b6e73f9b80ead06082779005
SocketDev~socket-patch~30YIXE.dockerbuild
21.2 KB
sha256:ccfa9d2a0b9950606a9695b9d45d5bdfe1baeab7312bbfc723a89f09f0d238d4
SocketDev~socket-patch~3X7D36.dockerbuild
29 KB
sha256:290b6d82f9889327a1b65dade88ddbb7cc34574ec677324244db6d76d7a4a4a4
SocketDev~socket-patch~4TW04E.dockerbuild
16.2 KB
sha256:27b4bf0f37c686e44643d34ddd69870f9bca0d8399693461fcff2b8d8addc0fc
SocketDev~socket-patch~8WAGH4.dockerbuild
35.4 KB
sha256:352594c327b907c1427975889c2c33ac355a99e0fbffece0d2a8c14ed4d36fc5
SocketDev~socket-patch~925XK3.dockerbuild
35 KB
sha256:d367187630ea835483362b904fcfaec84dca8ab824480cc50c0ea3a12f408b3e
SocketDev~socket-patch~941J1P.dockerbuild
34.8 KB
sha256:d15f14a9104b13983a92beea258fcc82f3aeb44b846f0577c00cdc2801a620be
SocketDev~socket-patch~AAE5ZA.dockerbuild
20.6 KB
sha256:4944d48beba1e4460fc1c8efe26dadc4d4940140b633c9fb0d091db1c8561559
SocketDev~socket-patch~AEK3ZN.dockerbuild
21 KB
sha256:3cbc2729c05ea91e0df7faeee7ce8cf95ecdc29211b09c58c0358ca3f7a886a3
SocketDev~socket-patch~CU6Q8R.dockerbuild
11.1 KB
sha256:53e136745858ae2f3c36bbedc1eab8f9ccfbdc7c20112c51de85e138f15fb43f
SocketDev~socket-patch~CXMB67.dockerbuild
33.9 KB
sha256:d428af149cde09beaa09098c223019c050c6ced9f77ff6592179658ebaad7fe2
SocketDev~socket-patch~CXRBHI.dockerbuild
23.9 KB
sha256:cfc36d5fb0964043beb8ca511da2f66c23d4968392e8ee9362b0afeec078827b
SocketDev~socket-patch~DD1RNY.dockerbuild
35.1 KB
sha256:6889e849d78aafeab1a68461caf7e573ddd5c90dedfe5ae14459ae12515965ab
SocketDev~socket-patch~HOAYYX.dockerbuild
17.9 KB
sha256:ca213ee4202fe827aef3f15e35f8673a0d5266d77ff6955fb786b5c6f522da1b
SocketDev~socket-patch~I623EP.dockerbuild
17.9 KB
sha256:6323953f6b6cce9bc0811496f97958ba770d07366324ffee0c1d310e99f307d8
SocketDev~socket-patch~I6O0WH.dockerbuild
34.1 KB
sha256:96b1885ce747b9f9b97f5df07700df8ce90231d3e8f7ef344c26013bbc8730c7
SocketDev~socket-patch~ICKDLI.dockerbuild
35.7 KB
sha256:5da54c3550d006b296ac6d2a63c09cee6d2e8f8acf5775c981d9eac5e71cd296
SocketDev~socket-patch~JP6UBR.dockerbuild
30.4 KB
sha256:e76d119e8e06747801916716971d9448d74db6c52be817fb1fb7135d548c9b47
SocketDev~socket-patch~JURRWQ.dockerbuild
34.9 KB
sha256:d8ea99ad5eb05a9f0c65c580e697a3ee923aa4658b6d92593cff2faedb266118
SocketDev~socket-patch~K4T0CL.dockerbuild
21.9 KB
sha256:940be98f4f6b6d90c935fdb9ed00a3cd31c0c6464889da73b054cd67fd72db5a
SocketDev~socket-patch~K948E9.dockerbuild
21.8 KB
sha256:5550430f919f3a64ebcb1618e5de3bb8e8bdc1e6d8b7833de5387ce6fd933976
SocketDev~socket-patch~KCTGAP.dockerbuild
35.1 KB
sha256:0ff54fdd74b1cf65fbe68453fef0c0fca8d55d5bc9a5a51783d832f45099a0ed
SocketDev~socket-patch~KSVZV9.dockerbuild
11.4 KB
sha256:f775d1bc9fd878ac84f2739b52f79cf649924ffda03e922062288fb436d8bacc
SocketDev~socket-patch~M038G7.dockerbuild
33.8 KB
sha256:04522545ede437ce41dee8a009a7c7fed22f5d4b7433a8dd3f1aad88a3a4ba6e
SocketDev~socket-patch~M4EFXH.dockerbuild
35 KB
sha256:a48c225b75afd0ac207fbe90fb5894b96e952bc2959a767b502a8184c8457c27
SocketDev~socket-patch~MFJEV4.dockerbuild
28.6 KB
sha256:b26a0aa958fe49a951c7ca2ab52394db69e5bf305eb85a8c25efaa6ccab7f12f
SocketDev~socket-patch~MJQ2BI.dockerbuild
34.8 KB
sha256:3bd650dd4d0c4939194802190970169eba8e16bccaef66d102556eae0f4571a2
SocketDev~socket-patch~MSAMQK.dockerbuild
34 KB
sha256:5c2c497c2134882a6ddd1ec70dc5306aa5567c885dacc4440adc993e49534fb8
SocketDev~socket-patch~NJAOYL.dockerbuild
33.9 KB
sha256:7f47baef5227b628194d052dd7e43f1924ae4b39353f5cc8a505579078bbefc7
SocketDev~socket-patch~O5WT3Q.dockerbuild
21.1 KB
sha256:6eaf71c8933d345df136cb660a13991b7723cb5b6fb321086ea5af70cff237af
SocketDev~socket-patch~OJMV9B.dockerbuild
24 KB
sha256:2a59934e230a673d642b89966e007e2983d5bd8509d1349c5e5096b94b64eec9
SocketDev~socket-patch~P3FQXS.dockerbuild
10.8 KB
sha256:7c6439dd9dfc216acb8b6efb19d1210e048da8bc11546c931e2d376f6a41022d
SocketDev~socket-patch~PAY927.dockerbuild
23.9 KB
sha256:d9ea5baf28c4c463fa20a5c332439b5f56bd88f987e8ce60c632a1ed17ebc094
SocketDev~socket-patch~QZ5DOM.dockerbuild
24.6 KB
sha256:b492b92aa2c73ad3e58ee47573088a65b88a157c7e236e24c12e2e79ee7e4413
SocketDev~socket-patch~RIB7IY.dockerbuild
34.4 KB
sha256:017eb2df6646a2d7988a5bdfec4a5cd6552e1b59aed4cfb72b90b3e948fd9d32
SocketDev~socket-patch~RVKW2Y.dockerbuild
34.5 KB
sha256:f33247f0a06eee03f3e3b42347554d22f0caaef7f0588bf4dcac94b53b92f20d
SocketDev~socket-patch~S9MBDF.dockerbuild
34.7 KB
sha256:3538c1377c4023ef563c728bfa59edecda213c6c35a68810ca1e3fea6cf8f4aa
SocketDev~socket-patch~T6PP7K.dockerbuild
34.9 KB
sha256:42738cd7e6c0aa4ced9105ee83616d24dfb5e2b26f8c8d8a600441a7ac551674
SocketDev~socket-patch~T6WZPG.dockerbuild
34.7 KB
sha256:4c740a2d70ad7cf4ba6460a9d264ba17a0b53c493e1ab326cd6cd9031a407ef8
SocketDev~socket-patch~UH262A.dockerbuild
21.1 KB
sha256:5e942957c4c92ee170c646744e32245bd820085bff07879b54a3e2877d95ba67
SocketDev~socket-patch~UYIANO.dockerbuild
34.6 KB
sha256:8fa39a7dd32461b8594fbd7f0344eca58a68468206fdfd944544fbcb7aa4aec8
SocketDev~socket-patch~VZJ5BD.dockerbuild
35.5 KB
sha256:380cd54d445323b48a2bd0b50e002a471233e1a4ceeaa814e25cdd245b8b7927
SocketDev~socket-patch~W1OS9P.dockerbuild
34.6 KB
sha256:16654de08588fb4eb282a11af390206d5dc2faaac4a3f91f7f639914a83dd0a6
SocketDev~socket-patch~W8T4ZW.dockerbuild
18.7 KB
sha256:94725928fb816f560c3e9a8cc62ac3b2d43cb1700028efa9f8277aca3ddde1e3
SocketDev~socket-patch~WBZ4HM.dockerbuild
24.5 KB
sha256:a5b94fdfdfc386f4cce58e72adfa061a7e6e05cd3ef8242fe03d8784f45bab81
SocketDev~socket-patch~WPBVWQ.dockerbuild
35.4 KB
sha256:49cb7377fb9a43eca7af5f08d44672c112faf8421dac76b0e8066d397f37795d
SocketDev~socket-patch~X45GHS.dockerbuild
22.3 KB
sha256:54a04ffcd55dbd7255356e2d5a7c243edcd4e8639fc009ab3e25890dceffb721
SocketDev~socket-patch~XOF6PJ.dockerbuild
21.5 KB
sha256:a36b59f431c1d5d887c623dc0945d7ba5630abbe2be9ca6f12a88f143a67c604
SocketDev~socket-patch~XRILOX.dockerbuild
24.8 KB
sha256:725fcc34caa871440d8381c66e529f999e543a46a8710ea6bfc5a91a23c8f081
SocketDev~socket-patch~Y93O8D.dockerbuild
18.8 KB
sha256:7b8fdbbf3e3630c83dde7666bac8f71e1a7914e75ea62f8c99bf513f82221a6e
SocketDev~socket-patch~ZQ7QV4.dockerbuild
34.5 KB
sha256:6d7ddda56ebb9635d1e8b9cd13918aad35bbc40affc9fbca94aa592d18b93783
SocketDev~socket-patch~ZQW42B.dockerbuild
35.4 KB
sha256:39aadabbdb37bc84c6842c068d1a1746ceb7ad55f54bde52dbd9b67018d08450
coverage-docker-deno
86.7 KB
sha256:7f152ca22f8f660549b532a16afc4c95938ed441dbcaa90b792a8b43a0db2409
coverage-docker-gem
86.7 KB
sha256:98a0672be2be56f31b5434bcb60c4f7c3e483a0102737ba286a225044b6c2b89
coverage-docker-npm
86.7 KB
sha256:f48db3904d50a262d10b652949b545855b052d7d38041da579643c0e9ce306fc
coverage-docker-pypi
86.7 KB
sha256:a5d118190019acc1ba66a1c56e9ed0d64e56fdf60f24191134ff938def527dfa
coverage-host
300 KB
sha256:15c681b9cc3118c5a7f3b20465d00901ab5bdd71182ad75fd60882e4b0b6f14c
setup-matrix-cargo
927 Bytes
sha256:d2a52e94d7efbcda739569540c17972e79f073273912e4ae7467d64b58f87fa1
setup-matrix-composer
926 Bytes
sha256:14c2c1ea908733b781178bf70e3511aee076f17abf61859ee5cdd329814aae6b
setup-matrix-deno
910 Bytes
sha256:0d4663f9c79b54f0f838b136da5ab0556b15331b4282a963679d4cb6d1aa931e
setup-matrix-gem
922 Bytes
sha256:56609c8f2b5de5964362d7e0bcd4d411bb36df0c8dc4ebc282178a1590bba2bc
setup-matrix-golang
906 Bytes
sha256:068db5d8bf0c51c34cf4fba56faa50616c24b6b5148e907dd15d4abc5777baaf
setup-matrix-maven
918 Bytes
sha256:a26ed27a71f887747d0e36cc9d77390edc5479e394abfd0d3e73691dde741d84
setup-matrix-npm
1.76 KB
sha256:2ddd37ad76fc45870a81e5e2a96add9486e787be3a56cf46923e86af67fa1073
setup-matrix-nuget
914 Bytes
sha256:95370828c509b8cbac91fe4b292dda133794e8b2df62a412c0ad521fd8fe246e
setup-matrix-pypi
1.88 KB
sha256:2eb7b47173c3d741c9312c1f560ef8a618d2cbe300171c84cda385efd525b100