Skip to content

feat(vendor,scan): lockfile-driven discovery + verified auto-fetch of missing packages #323

feat(vendor,scan): lockfile-driven discovery + verified auto-fetch of missing packages

feat(vendor,scan): lockfile-driven discovery + verified auto-fetch of missing packages #323

Triggered via pull request June 11, 2026 23:04
Status Success
Total duration 27m 38s
Artifacts 74

ci.yml

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

Annotations

37 warnings and 3 notices
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 (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 (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 (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 (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 (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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 (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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 (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 (composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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/
coverage-merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, 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_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_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_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_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_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~03A77R.dockerbuild
24.4 KB
sha256:de973d90ff1d44007b7bd08a4dc90e9e9953082404e1a05913a51c5240570ffe
SocketDev~socket-patch~0C6LRU.dockerbuild
11.9 KB
sha256:41f37db4da4c1dcf0b17f204f2a42205dff6d332d9c3d0a15b67fc24262d1373
SocketDev~socket-patch~0KLCHL.dockerbuild
34.3 KB
sha256:6cbfdda5595cd51f1452597c987488b120b5c67e65bf583c7bdbe82c6f436228
SocketDev~socket-patch~0L69YA.dockerbuild
16.2 KB
sha256:3224c42e8e5db017dc3b0a5e6fa13650a1b1d4c167f528fb184c6e364cbec826
SocketDev~socket-patch~2J70R6.dockerbuild
21.9 KB
sha256:33804870e4cf5fa2c8228f33a4cec6088864b209e45764e0edc35bf89985334e
SocketDev~socket-patch~4N5CUC.dockerbuild
11.1 KB
sha256:c9fe37be95af170f4f5fc64dc3b1207a39a3b8631e26844b461cd46e285f2dad
SocketDev~socket-patch~95NCPN.dockerbuild
34.6 KB
sha256:ff284fd1ab473af481e175c4279db96b62e69bf96131b79c18eeeca26b2e5f70
SocketDev~socket-patch~AXAVVX.dockerbuild
34.8 KB
sha256:1a8aa59898c810facbadba1e6ba4018fc35e685b197ebee63c65ca78b6fee80d
SocketDev~socket-patch~B0FILU.dockerbuild
35.1 KB
sha256:e8c5ac2461701d9eee3621fce738e5d4fe4a4bae6597cd36047d325fd13712f3
SocketDev~socket-patch~CC4C5C.dockerbuild
34.7 KB
sha256:9ca0fd91c63e18dc679b868531a9da332516eba97c497c6e335015a989220369
SocketDev~socket-patch~DBSKB5.dockerbuild
35.6 KB
sha256:bbd01d895ed828b4f5c2509f421a8b268fb9d19ce613ab8bdc7fa8789edc4d0c
SocketDev~socket-patch~DBX0N1.dockerbuild
21.3 KB
sha256:62bdc0eaa840917941fe45f09142527f693b2391a8240606f7b840dfbe0bf147
SocketDev~socket-patch~G4DNA5.dockerbuild
34.5 KB
sha256:987fce0c8cba80b1f2811119b110f0e180d6325d6d253da664cd4d6dfe107786
SocketDev~socket-patch~G8FOBO.dockerbuild
21.3 KB
sha256:56c680eafacae73bdcb59390e325926735148928fbb32b4c585ca4eda94d3aef
SocketDev~socket-patch~GH1FQR.dockerbuild
23.5 KB
sha256:d1f0bbe95a03561bcc60eb01b72496c6803cd8b429ddad2cb4425770d50ae401
SocketDev~socket-patch~GHI7OH.dockerbuild
34.1 KB
sha256:4164c507247b36d65af82d5337bc73cd55d72758a0e1933338a910408480713a
SocketDev~socket-patch~I5VLI9.dockerbuild
35.4 KB
sha256:e37de16f779b98e2e05844182cde190ff49a09254af3a575113b9414b0ca2db5
SocketDev~socket-patch~ILVYUH.dockerbuild
29.3 KB
sha256:b5296560409ee462809e232aeaea6a9bef4254c89d42d4563014cf4a4cdb5cc9
SocketDev~socket-patch~ITRVIJ.dockerbuild
17.1 KB
sha256:07d1e2c832c00a4436e8cbad60f59b060892175ca85071c9dc66819c073e0f21
SocketDev~socket-patch~IWNFGU.dockerbuild
35 KB
sha256:676debe7d1c537e03651f3ebac41a5c3d2f2c1cd29231d2305048caf7bbf03bb
SocketDev~socket-patch~K3HQLB.dockerbuild
35.5 KB
sha256:99c36824fd036afa5e5eb9f0f363662a18a13b1531013b1a8775aedfe099a7ba
SocketDev~socket-patch~KVLTV5.dockerbuild
34 KB
sha256:63a806eb2a8f6232b543811fb38aa49a22f894f842fbf0ff44d64d84e375da4a
SocketDev~socket-patch~KZ1AWM.dockerbuild
18.8 KB
sha256:375562528205b5360e1ad03d4079e4af8d26c840d6fbeee7fe91101e0c68367a
SocketDev~socket-patch~LW5NWZ.dockerbuild
21.7 KB
sha256:07afeac6cc67850d1cc7b4d4f605c13c2e3274f4f6c121b250f64e81d8d06997
SocketDev~socket-patch~M2APR1.dockerbuild
19.2 KB
sha256:c7a846634ed68d790cf0008c5fbb61f595cd97ab0b2be751dea95341a59f523e
SocketDev~socket-patch~MHHHC1.dockerbuild
20.8 KB
sha256:556b120c944645f32fd0e90f91a4860bb2349dd5fdcfa348a4b140c007ef1ceb
SocketDev~socket-patch~MN87VP.dockerbuild
35.4 KB
sha256:39518a7bb82de6dc2ae7d13e0e853cdc818b8ccbbbd7310108cf5423db39cb6a
SocketDev~socket-patch~N0T0XL.dockerbuild
34 KB
sha256:25e0b59d90b07decfcbf71fdb823022d045116fff45bf1463899b845e8e1508a
SocketDev~socket-patch~N7QRD1.dockerbuild
34.5 KB
sha256:adf4961a8985a255e91b78d9a2040562513dc2b27b2f2b0683e418ed405148a5
SocketDev~socket-patch~NB8V76.dockerbuild
21.5 KB
sha256:f8e2d28f99d18456926b0d66de5b2db92596de42ddb67560c2694ae99f17636b
SocketDev~socket-patch~PA7K3Z.dockerbuild
20.7 KB
sha256:07334869977e6d4c54149b78db62544b18174ca5e2789bcfcce78d8b2b34cd83
SocketDev~socket-patch~PIRUFJ.dockerbuild
24 KB
sha256:8fe1d1505ce97b84f8aa5aba3350ffe428ef05832d77fe16b885f90ef2511759
SocketDev~socket-patch~PO6DJ6.dockerbuild
34.3 KB
sha256:c523e0c7ef327e64b7c8a6a0e72685a50eb90af535f4078fbcbbafe0f5292111
SocketDev~socket-patch~PYS7SQ.dockerbuild
25.1 KB
sha256:fad23aaaba9831fa4b1265cbe509c1d16b9654d58c96a5175e876d0bf6a59dc9
SocketDev~socket-patch~QG0REG.dockerbuild
31.4 KB
sha256:78d0d6d0abb842f81adfb2a65260d5f6590ac6346ee8398d0190f0c78910fcf2
SocketDev~socket-patch~QO83NG.dockerbuild
24.8 KB
sha256:99491d6f91bde7de689a0fecbca18f15abb781cd02f40c3188bf261bd443ba53
SocketDev~socket-patch~QYM4RG.dockerbuild
11.7 KB
sha256:de31d8ddd48e9782982934cbfaf4cede9b3848d8ae176b309d31a0328bd61b7b
SocketDev~socket-patch~R4IZGX.dockerbuild
34.9 KB
sha256:dcd6427501ce7c8a677dfdaba99e7e006eea7d5432d20c93ecc1be93f9824000
SocketDev~socket-patch~T0HOX7.dockerbuild
35.6 KB
sha256:bda193ed6c104abb066a5202df372f2102c7085388a73377710a27d719b8ba0c
SocketDev~socket-patch~T4GQFK.dockerbuild
23.6 KB
sha256:4138bc309f25efd2da248c325b20b099dcb2ba990804e6ccc18bef2e4b943570
SocketDev~socket-patch~TRB15L.dockerbuild
34.7 KB
sha256:0dabf3cc642a0b8e270e2df8b7c7b91d08491506021ddbca035a01dd7e4fe8ee
SocketDev~socket-patch~TSA5XN.dockerbuild
34.1 KB
sha256:f69c5aad0c69751b9b91b22967d8ec202261a1937649e5f3b3e4ec26b3cae767
SocketDev~socket-patch~TTVR4Q.dockerbuild
34.7 KB
sha256:c8caa856f670a7d2f7b864573324ff53933a40c69a30bf47358dd2266b298a20
SocketDev~socket-patch~TVL63M.dockerbuild
34.7 KB
sha256:7980e85a1a2fe62dc52c8fbe49c75ae9c9bb2e0c682fd2b6574f5dbc57256833
SocketDev~socket-patch~VL9S10.dockerbuild
34.4 KB
sha256:1c32587ec43c37afe23af2356745505fe7d0db57dde49cb78ffd69a094ae4ec2
SocketDev~socket-patch~VWR8I8.dockerbuild
21.7 KB
sha256:08e6838b56c1757e55f5ab6467bb99eba80793c29a2040f2af09fe568107d2dc
SocketDev~socket-patch~WFYUAQ.dockerbuild
34.6 KB
sha256:fc49fb73b67db316972b5982216bbfd6265db206eeb1b046bcd6c9b407c66895
SocketDev~socket-patch~WG0EN8.dockerbuild
17.7 KB
sha256:451e95d3f277d3fefb7bea41e9844c4ee02ed8900a7e09b2b9bdf546fa4cca18
SocketDev~socket-patch~WYGREG.dockerbuild
35 KB
sha256:3d8a8824ae88cd4a8f5c296adb95bf848698bd29594e7fd4f4770abb57644310
SocketDev~socket-patch~X8YJTQ.dockerbuild
34.1 KB
sha256:18fa55dab62b1581d14fc16504fb461c16f729b71914e5d865d4b3380b727481
SocketDev~socket-patch~XLI67H.dockerbuild
19 KB
sha256:fca2f93153a227cf136adc4edac6f0a4e81311823b9fdf9300e2cf82b8d94120
SocketDev~socket-patch~Y5QS85.dockerbuild
30.1 KB
sha256:f1170e6fae0d41d316b0b83edb22e7540940e7b43bc87fde057db0704af7adf8
SocketDev~socket-patch~YRP08F.dockerbuild
35 KB
sha256:f65473f5ead644a2fcdf6fe4fdff623851f4b78713214152b9a130f8702ccb5f
SocketDev~socket-patch~ZIXDL2.dockerbuild
21.2 KB
sha256:5e20acd0235f7edb023c97a1d0ad975104e453beaedff15cf2e85d4dcf86c9e5
coverage-docker-cargo
86.5 KB
sha256:b825bd367f56226e9b1ad8a249fd35be0931842fa6958b7879e0acec98c40d22
coverage-docker-composer
86.5 KB
sha256:32f464007d425fd7e7c356e55e3757d65ff2220ac8e1017629d8f7a3ca75631d
coverage-docker-deno
86.5 KB
sha256:499afdd00e3c5fdca65fd5b0d6fca394b84ae476b86d3c4a13410dacaf3bc515
coverage-docker-gem
86.5 KB
sha256:fc3900991b29a10c5a441a217a816fe89b8d462c6e08870a09308720973ec35b
coverage-docker-golang
86.5 KB
sha256:9d91a34fa5cb96e134deecb8d472b8e285c348722cf7ac1c81e4982771a0bb5c
coverage-docker-maven
86.5 KB
sha256:f67d11c7966f440031168b4bad15023cf662ddb06268db6170744beefcd96f4f
coverage-docker-npm
86.5 KB
sha256:f47e0c8d488d1f44386da3e77d3e4f9bf7125e9cd0a640949ebae1a81ceaf57e
coverage-docker-nuget
86.5 KB
sha256:8562e14b82db57fb9393789a89d0c7175f969fba202f2c5c14e3335b25a9f875
coverage-docker-pypi
86.5 KB
sha256:77e30080309ee8630bef57fe75540e4840b186d89e8edd874895efb3c48293ed
coverage-host
299 KB
sha256:4989de901caa20a7ab735ccddc6774062af29c127555a6ccb02820a96466b16a
coverage-lcov
307 KB
sha256:334d3e3c944cb27e440521a01a5e7008c605a904e958b1afadf32f4c1ba4c981
setup-matrix-cargo
928 Bytes
sha256:5a5c645a7e1a2538d84b63bc60cf7337e1aabc1c7ea128f3ca86d1d2cceae13d
setup-matrix-composer
920 Bytes
sha256:d17d339ccf7aaa8ae593e908f5a76c3cd12da783e110efadd68051ed0d607f12
setup-matrix-deno
909 Bytes
sha256:3fcf466a272c3b40d64112ae8f35f972bbea3d8e3b5507b6587e042f52622904
setup-matrix-gem
918 Bytes
sha256:842446c59a9916384a11b3b8c1bc2799f43801cf96071c3cb46a159fc5b0681c
setup-matrix-golang
908 Bytes
sha256:cb62f55861665051b82a676aba1eb3686041fd8dcdd6e15ce15bf58af051fb55
setup-matrix-maven
921 Bytes
sha256:9fa3c0aff1f39403d50a8455206b87d0246dba2f42b810e4eb9d2930488e189c
setup-matrix-npm
1.76 KB
sha256:9176a244a2d07891c8dee63816d29d655d4db4c8540006e8b4a500f3fb1f0fd0
setup-matrix-nuget
914 Bytes
sha256:6b0cc2283cc9921344bedb13bc02711b64c9ef5125d8037d6f777b40dbe1f112
setup-matrix-pypi
1.88 KB
sha256:94cbb7165cb0cf910cde3cfc4390f35a53ead70b6df943dbf621e2961c84bdda