Skip to content

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

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

Triggered via pull request June 11, 2026 23:33
Status Failure
Total duration 26m 0s
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 (composer)
Process completed with exit code 101.
e2e-docker (nuget)
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 (composer)
Process completed with exit code 101.
coverage-docker (golang)
Process completed with exit code 101.
coverage-docker (cargo)
Process completed with exit code 101.
coverage-docker (nuget)
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 (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 (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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 (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 (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_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_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_nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_safety_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_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~06WFMM.dockerbuild
29 KB
sha256:e44578ffe5d49d79000b34f45df1d83482d402c065c7d83e7eec29ec57000646
SocketDev~socket-patch~3GHR5E.dockerbuild
34.4 KB
sha256:ce7f5ae4b4bf3bde6c037a79c85a8e7d8913155c9b8618b1ef25a230dcedddd2
SocketDev~socket-patch~4JSEKC.dockerbuild
17.3 KB
sha256:905e35a184a4b98fbbfaef78500731856847942ecb600d7a4e1b8ca286f5ac32
SocketDev~socket-patch~59VPSD.dockerbuild
21.7 KB
sha256:2ec2bd62f35043fe45aa919888d2d1f14a875dfda401dfb3fa7c4a59ccfa49a5
SocketDev~socket-patch~6WAWTO.dockerbuild
25 KB
sha256:cf9a728c5e8e17bb4b7996193da4b1878a134461867f13d514a9164a2e862874
SocketDev~socket-patch~7E6FR6.dockerbuild
23.8 KB
sha256:aa2d10afe66bb9c6e77faefb074f137ac509c68e69c5d41fa02b76afcf587bb8
SocketDev~socket-patch~7OB97Y.dockerbuild
34.2 KB
sha256:eed252779791acbe17b0902069bdcf476115febceb89a4f7478e8849dc8adbb4
SocketDev~socket-patch~8EQPOY.dockerbuild
18.2 KB
sha256:7421d9bdae6ad13d705194e4aaf2a81df458bd217fa10a3e75133efcbdab9592
SocketDev~socket-patch~ASBDE3.dockerbuild
18.3 KB
sha256:822ad293e255fe196fcf8004144cfbdf3534fb3a67be4cd0418c46066a1832cd
SocketDev~socket-patch~BNU7WO.dockerbuild
34.9 KB
sha256:afceb1b96522d487a16b89ed1f803281d9b4b19dc806498857178b42caf734ad
SocketDev~socket-patch~G16II7.dockerbuild
21.9 KB
sha256:0b1d73ab8f59b39ce2cae6a029fd48ab61b1a0988eae8607ee4bc8ea2b8e8402
SocketDev~socket-patch~G7KYX1.dockerbuild
22 KB
sha256:326614eae343ff537c84cd235b718db4f2e86a6a0fa5a1e2edc04aeaf03c70d4
SocketDev~socket-patch~IV8R0O.dockerbuild
35.4 KB
sha256:9ffb6da6113ad4abd38743d4a96865302650c7b859829061b34f21d35b3ee111
SocketDev~socket-patch~J6PVOD.dockerbuild
24 KB
sha256:3e823e0527aa806f05a25221a15aa7c3d9e5a5bfaeef90930d94fbed09992d20
SocketDev~socket-patch~JC7K2K.dockerbuild
24.6 KB
sha256:71716a71b94908becc9cc8fb3695c111ab4fea4ef40bba5b2bf7e3535c9908f0
SocketDev~socket-patch~JFMZQV.dockerbuild
34.7 KB
sha256:663f5a2e736be1d19a528dd6622ede36dcee8fa14fb5bbd1cfced178e94cfb5d
SocketDev~socket-patch~JS8KU4.dockerbuild
34.6 KB
sha256:2f835f4c15edc8d0c9ae31195a8cdedbfb81ce464980d2e77d2028da23bbe577
SocketDev~socket-patch~K18O6V.dockerbuild
34.8 KB
sha256:0ac27345c9e38d4c4fff8251389c6a727508c8a432ead87ed6204e5f177dd65f
SocketDev~socket-patch~L8T01C.dockerbuild
11.4 KB
sha256:07766fc4abb17d0718b3eb9412b48a4453f1025cfeb72a0969c407774b381496
SocketDev~socket-patch~LA7TAT.dockerbuild
30.2 KB
sha256:90067bcc3652f3ee9d5d0e98227be080b5edf2bec13c23fe296c704f81ffaaf8
SocketDev~socket-patch~LXDO2T.dockerbuild
35.4 KB
sha256:352b0fd71cc27a4077cf1685da5715f527e6ebb2c315734bc067e84cfe174c14
SocketDev~socket-patch~M5ZGLO.dockerbuild
35.2 KB
sha256:827fc9f2e77784692c2f41681ed4220c34688712a1253df4891ace0e228348a3
SocketDev~socket-patch~MWGGNU.dockerbuild
34.3 KB
sha256:4416d38958a05ed35b63fe8d27feed28ecbf459c81f08c0c454a3f11340f813c
SocketDev~socket-patch~N9EZI2.dockerbuild
35.1 KB
sha256:790c301a9ef7c271ade40e6d1f08cd610fe9377f3d4c3813200656a78692342e
SocketDev~socket-patch~OUQPZW.dockerbuild
33.8 KB
sha256:81bb57247b5d98cbcd5fdf5748e8e76bc86ccc7eb81cd3d3c526dbeabd73bed0
SocketDev~socket-patch~QG0RWL.dockerbuild
21.8 KB
sha256:e10ee26b5ade79760b5d71ab95a9aff38940546e9c66de03ebe1c36bf49f971b
SocketDev~socket-patch~QUU1RN.dockerbuild
10.9 KB
sha256:e94494bc605f9b8b713dd36e5f91fb34839abe77f458de1f85e0ae90f6f853c5
SocketDev~socket-patch~RCWP60.dockerbuild
35.5 KB
sha256:f66a1ffcbbbe8f3793efc4c65b66e3e6645e021fb3052ae8a7cd91d395cc7015
SocketDev~socket-patch~RGOC2V.dockerbuild
35 KB
sha256:27764c0cf2e0f7a5f150751526f1b94288d78097b53d3095cddb3486c5ae0710
SocketDev~socket-patch~SBTI77.dockerbuild
33.8 KB
sha256:8bc30c8f9218f7269f8884322ba7600bd5f52bfe0450acc8866ed13eb6273063
SocketDev~socket-patch~SDQ95U.dockerbuild
35.1 KB
sha256:cde4104ab239ec1f189015a0d9e051f08fa1df289efaf8b0e0c735dfaa9ddfd4
SocketDev~socket-patch~SSR34P.dockerbuild
34.9 KB
sha256:6f5cbd3e6d4077e2444282be094681a732aac7abf57f3cc10d8f8dce370e3554
SocketDev~socket-patch~T2PTWR.dockerbuild
16.8 KB
sha256:a51ed661e52eb8ac6997ffec71a643040ebe7be0d31682fc4d239ff720e17b67
SocketDev~socket-patch~TIQKFL.dockerbuild
35.3 KB
sha256:8329cb612c6d192ffefe8928186dbf7065b930af71a8370a07c2cd3a35ef9d7b
SocketDev~socket-patch~TKSJY2.dockerbuild
34.6 KB
sha256:42eba37005d4d4e9893ec12257b0ad91463e04dfb7de1f18b8e3f0c8d9328dfc
SocketDev~socket-patch~TT5E5Z.dockerbuild
36 KB
sha256:8035787dc64ac74b86c92fd0255cc879f16b8e5304005a71e435f46fddebeb57
SocketDev~socket-patch~U04IRI.dockerbuild
30.4 KB
sha256:cd4cbbad9ea2b42143a51a2aadaefbf814f47a4cc9158aebefc969d9403eb671
SocketDev~socket-patch~U1DWWT.dockerbuild
34.4 KB
sha256:b7f3272f9c8876721521bf352b5dcbbfa19745da63f96b370cea381fbec0a340
SocketDev~socket-patch~UCGG1D.dockerbuild
16.4 KB
sha256:b6a7adbcf71cedc2a3dbcf1b85582f2062f500077967dfed1c8212888307bac3
SocketDev~socket-patch~V78W2D.dockerbuild
34.4 KB
sha256:6f996671ba3199e6a031f3b20240612acdfd0676458bb737fe8a8e95f694d118
SocketDev~socket-patch~VEZNZX.dockerbuild
11.2 KB
sha256:721d596243dabbf5763b061dbd0caf76ca89dcdf6421af3c038de49c5b7c21ef
SocketDev~socket-patch~VV1WJJ.dockerbuild
21.6 KB
sha256:81a5759e841e964b815b65b0f32168ace7b1540e59239c40d24b2b183908add5
SocketDev~socket-patch~W068R0.dockerbuild
18.2 KB
sha256:9bdcffbea4b23606be3f1676210af237ebe0866e9793c1919a6b9837810cf5fb
SocketDev~socket-patch~W55UGP.dockerbuild
21.4 KB
sha256:1fa7d786b0fcfc85817255839f2fda702e90df32a62a97519678f51b73d59ee0
SocketDev~socket-patch~WB82HU.dockerbuild
21.4 KB
sha256:9f52032e28b9ffec2e0c94bb8eec40da65129a88bffaa57e8424201e6b1c722a
SocketDev~socket-patch~WGTK4R.dockerbuild
21.2 KB
sha256:c8bc487382a997ef339f91b1467ab03ca264d85e07665e78ceab4cf285b2a4f5
SocketDev~socket-patch~WYH66E.dockerbuild
25.5 KB
sha256:af4174d7101f1c38e2fc72fb9195c62d7a840625bc4af18a89f3943b34f76a8d
SocketDev~socket-patch~XM0B65.dockerbuild
34.8 KB
sha256:7abbdbaf51397fb4002e15b5e039f1ea1d2927196264d260e6f42d218a549b4b
SocketDev~socket-patch~XN564D.dockerbuild
34.4 KB
sha256:617dc6d6a950d50964a94254e5f5a68f25b004c52146cd4d5d47fa9b7892da0c
SocketDev~socket-patch~XYR1TB.dockerbuild
35.2 KB
sha256:d736d5e05c5d54ce105cc5a36c37ef621c63439853cfc5951831e21712008566
SocketDev~socket-patch~Y31QI6.dockerbuild
21.5 KB
sha256:e6dd42ae4eae0611abe6c0eaff004facb194f1f5de32613b4d6af16c3835658a
SocketDev~socket-patch~Y5JHG6.dockerbuild
34.2 KB
sha256:554b287638464d4a79fb854237b95403cfe108a14e26113d82bb74fb3cf32828
SocketDev~socket-patch~Z2V1Y4.dockerbuild
35.1 KB
sha256:3e03e49b92d8b18180eb8a735153b36d54ca0c71ca16a4fd8f61822ded96445b
SocketDev~socket-patch~ZV1UB0.dockerbuild
24.1 KB
sha256:96b84053f1c62b244e7985c47e952085609f7ed79fe7211ab8589ddf9290bea2
coverage-docker-deno
86.7 KB
sha256:f6e88a875613ba948e08b9b6dcd8b51df8f0a5dd5a744456219b34f407334a87
coverage-docker-gem
86.7 KB
sha256:77a76695c13c6865c9ee8434168ecdcaebe699993f9b24839602dd199726108b
coverage-docker-npm
86.7 KB
sha256:09c6560ecc17eb2de8d4832ff695156f6db6637fa46f3e8ef6365d4a52298b4a
coverage-docker-pypi
86.7 KB
sha256:232edb774c45ea7c9998225d45731b512ea0dc86f5559beb6a6cc37d41aeadce
coverage-host
300 KB
sha256:0ff36863b1d4b73a6c7fe52c4535a052b2d912b825c1a8cc0483d799e9d12f38
setup-matrix-cargo
932 Bytes
sha256:66c30d59502a000dda76751e303b4562d6100e7e04bd14867e35caa4982f067e
setup-matrix-composer
917 Bytes
sha256:e3de8aaa1d76e926130b69621f0cbf6ab1eced59e2ce7f0fef5ea7d6df10bcb9
setup-matrix-deno
907 Bytes
sha256:d0fa6daf02f9b9520b50661c6ea80c8dbbc67164a3bc9d2f7f82c619b7940894
setup-matrix-gem
922 Bytes
sha256:7e5a2ffda1f5e2d3ce45d94ec631469eb57a233fa9e9a38525138ddf484577d5
setup-matrix-golang
905 Bytes
sha256:0e940e362d9f90cf22ea4f5ea81eade3039c705fddb92d64e790c077c1f3c10a
setup-matrix-maven
920 Bytes
sha256:c85a3a39205fe9233c3c607367ebdceaf71ee1b86aac8537dcd2a4a70b5584bb
setup-matrix-npm
1.76 KB
sha256:498e5378249aaed5981757210e7194f05841cd286283a4985178d9e82a469758
setup-matrix-nuget
912 Bytes
sha256:ac747ec0bdb66106d9031dba4ec82565b2489fa25f2f59d612020c8b89897e53
setup-matrix-pypi
1.88 KB
sha256:1bf9d4d80dfb246d2067338467bf9146af7cca8f902a7ab7865ed88bc4ed8cad