Skip to content

feat: vendor/scan/apply overhaul — lockfile-driven discovery, verifie… #332

feat: vendor/scan/apply overhaul — lockfile-driven discovery, verifie…

feat: vendor/scan/apply overhaul — lockfile-driven discovery, verifie… #332

Triggered via push June 12, 2026 20:59
Status Success
Total duration 27m 0s
Artifacts 74

ci.yml

on: push
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: setup-matrix
Matrix: e2e
coverage-merge
34s
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 (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (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 (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 (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 (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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 (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 (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 (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 (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 (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 (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 (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
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_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_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_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_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_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_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_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~0Z6FEF.dockerbuild
18 KB
sha256:7938f1f3465151879b37f74b724d1f6dc5f9b80270f9841a66f7816ae14e1015
SocketDev~socket-patch~11OMHY.dockerbuild
24.2 KB
sha256:2174b9f83c617c6c5ad5b0f50bed2f8eaf708e5768287a3df60f615f8d707b6f
SocketDev~socket-patch~4PKGYM.dockerbuild
35.6 KB
sha256:93044ec483ed87367f4f9110e1c2cb94601e6cbd4cf14cfc69daf7ec337309b0
SocketDev~socket-patch~4Q5AN8.dockerbuild
34.7 KB
sha256:73674dbf63ff147f8a2392680ecfc6f320b6c3fa5309e406cae37a043c7a903b
SocketDev~socket-patch~4S0SQM.dockerbuild
21.6 KB
sha256:b1116b8d6ba02d886939975a15b16db6fa9bed78d45beb57dd9ea049e7ba26ef
SocketDev~socket-patch~4TO05Y.dockerbuild
34.8 KB
sha256:978e62d77dfa39a149e5dd378ba0824f500cff54d2df551158e8b27a15185cb2
SocketDev~socket-patch~6ZPWS4.dockerbuild
12 KB
sha256:15b39c50f4640ffd83c5b736f091bbfc3fb5d7ae923c2065c7668953a1009528
SocketDev~socket-patch~73M4RO.dockerbuild
34.7 KB
sha256:f1f9e20bf719ae5267a02fa810f67409ff47907a74425b071eba605c05f6b515
SocketDev~socket-patch~7I1QC5.dockerbuild
34.5 KB
sha256:4ddccff98fbee18b36750c6fb5f78659bc6675f2eea382dd3e772745c8ac2c3c
SocketDev~socket-patch~7RB5N3.dockerbuild
35.2 KB
sha256:2bdad11e295c07b0a4b7bfb526511469d6f44225d1343722e2fc656d2d831630
SocketDev~socket-patch~7RB8P2.dockerbuild
23.3 KB
sha256:b90225b098df2d9a49e19393b3818e765231e534703ec1f502cfb3b48d51c9b4
SocketDev~socket-patch~8196EP.dockerbuild
17.5 KB
sha256:e59d1b38f6a0bd06a9527ba9606a8dc0b89bba2eba61a7f1026c41b628cbf517
SocketDev~socket-patch~8F69JV.dockerbuild
34.8 KB
sha256:f40fe7547f6590f32fb4bfa8d3850df61e105872a7f09de7a62f49b2085263f7
SocketDev~socket-patch~9HHQ7W.dockerbuild
21.3 KB
sha256:9403211e686b1fa1eea9c036f9c34cc475a30a0e6073deac237bb70c24af4c82
SocketDev~socket-patch~A7K1RZ.dockerbuild
21 KB
sha256:0d827510373ba1ea333e5a0f088e05a36414a97d4fee570321107935612c5a0a
SocketDev~socket-patch~AFDSQT.dockerbuild
20.5 KB
sha256:cf9ccaa99f6ea8ed63d9c6caff740b851d0accb61fccacb2a937607cca5d45b2
SocketDev~socket-patch~CBQV10.dockerbuild
34.7 KB
sha256:38704e722a407b103f631c56828b28d7cd34d0034ce39d6e8cf9378c00462da7
SocketDev~socket-patch~DYS1Z4.dockerbuild
21 KB
sha256:695dcfde5b3285bd965c9ced04e36579e7bde4969355b426d03ec718e8e0e9f0
SocketDev~socket-patch~F1NZQG.dockerbuild
34.4 KB
sha256:34789cca8faa1874040f6f65e5859caee2c61def925c4f8d0cbb193a04992094
SocketDev~socket-patch~F5OD3Y.dockerbuild
35.1 KB
sha256:d899016c60d759a675fcb8fdd55822c6b133e2a8ebd48c2ba9fd8d6850e27dbf
SocketDev~socket-patch~HLN5SN.dockerbuild
35.4 KB
sha256:75ca133bb75e0852073da9ccaa62a072bc4d1cd2c54272f7e21447c4d935621b
SocketDev~socket-patch~HR9T2M.dockerbuild
34.2 KB
sha256:aad13cf2163185db78ec634c99261f25ad9348f5daf516e79a0bfd1401f94986
SocketDev~socket-patch~JCSL5G.dockerbuild
35.3 KB
sha256:9b776dedcbc0443f5c9c8cd6ed1c28640984b41ef8b7b2ac9904199ac1a30b1a
SocketDev~socket-patch~JHAC9M.dockerbuild
11.6 KB
sha256:75239294ee1699296d2dcb5f6757fa39d556fc4eb40362d1542fbe9e9f7348b3
SocketDev~socket-patch~JRQ45V.dockerbuild
18.4 KB
sha256:546c9a1ec7738d53c738dc2691a42c65c6b03a0fdfbffb4109ad695157985b93
SocketDev~socket-patch~K8TKWC.dockerbuild
35.4 KB
sha256:1045c8f9892245aa14d820a7683677168750ed184afff6fee2e041a03f5b9c1a
SocketDev~socket-patch~KRESEO.dockerbuild
34.3 KB
sha256:fecf51abe8eab3cb607273b9050e4b898081271abfe4d026b5891542d3739370
SocketDev~socket-patch~L32J6Q.dockerbuild
34.6 KB
sha256:4ec9a4f987d9dac742abd4285d6d9f72e9428a92d4d8a915256fa15d7bfc1ab5
SocketDev~socket-patch~L63BRZ.dockerbuild
16.5 KB
sha256:9bab66d1ddef1a01a51d538a368d522e4a2b5a6dc1b004d8eecf583c4326e33a
SocketDev~socket-patch~LGYY26.dockerbuild
22 KB
sha256:f27543934ef01ede564bbc9178ad779001aaec0559b0735867c22e1b642771a4
SocketDev~socket-patch~LP6CFC.dockerbuild
24.8 KB
sha256:1f86074f195b1488176b39d00f88a270b0c7f134053fada13cdce9513dd9d829
SocketDev~socket-patch~LSD65H.dockerbuild
11.1 KB
sha256:2f6f3ba462059b504798211b2248ca7618bed16a823b8fa8729e0f3aa039058d
SocketDev~socket-patch~M3CGSN.dockerbuild
22.1 KB
sha256:4ed7736aefbcf807f8a56ea03c50e41c00a8e0f9580220150bbca2c1110b6e6d
SocketDev~socket-patch~M4FCT8.dockerbuild
30.5 KB
sha256:6aa0db008f462ef833a400d6e7a10b62d820bc9123b6be71c4218c86bf94e1a7
SocketDev~socket-patch~OL5QZD.dockerbuild
34.5 KB
sha256:d64562544c686770c250a3f3731d8dec7cd6f3bf624cf683304d2b31fbeede99
SocketDev~socket-patch~OMWG5G.dockerbuild
21.3 KB
sha256:f48e57de0eaf5aba02b1a88df988d8d126b1df1e43fd4a8a0a731fbc26a2ca60
SocketDev~socket-patch~OYR45K.dockerbuild
24.6 KB
sha256:f54f2e88759e60af1888ba839f9748a458ed6ee4f97e097037a6bef44bd741e1
SocketDev~socket-patch~PFFAPR.dockerbuild
18 KB
sha256:68b7e2b42d3cf3fdbbae899ce0f18f94b2ba343494fd9713b82819a6726e5dbe
SocketDev~socket-patch~QKLT7J.dockerbuild
18.5 KB
sha256:2cfaa7ba558513f0a258a27b177acea3bb17135e92aaa9929b0a5569528560ac
SocketDev~socket-patch~QYS1EO.dockerbuild
35.8 KB
sha256:be0cb3da4582a32df02ef56aeaac7db1609984f4f61ad2257cc2e7bfcac9684d
SocketDev~socket-patch~RMSQT0.dockerbuild
34.4 KB
sha256:27b9d8601558f1da6eb73e2ae8ba3c0dd4c8d1ae0c3469aed1f175bb438c0f7d
SocketDev~socket-patch~S2VV78.dockerbuild
30.9 KB
sha256:5aee31390c34c0e4cf27b94d1522b1b66e93cc9cee758500864f2378d5d2a066
SocketDev~socket-patch~T321SX.dockerbuild
34.4 KB
sha256:cc65eab344f31097fe5c896d2864a54428ddfa8dc6d653c416f09ffaf284b8c5
SocketDev~socket-patch~TPF1HS.dockerbuild
23.9 KB
sha256:71fb6ff0911e6b46c1a676d453be3d0cde475e9d62a9f45dc50a2745da44f95e
SocketDev~socket-patch~TVXA90.dockerbuild
34.5 KB
sha256:2a7f85e149d22d49040f5395edb2b9bda4b16d836dfe084f01c53f32ddbbf09a
SocketDev~socket-patch~U8B7QE.dockerbuild
22.3 KB
sha256:721d274295cdeb430b2bbe32a081d8754b4f1619dc078ad5dc772be56e894046
SocketDev~socket-patch~UV81LN.dockerbuild
35 KB
sha256:045d367ed4c08f13978c3ff9797f154b09938503ea4719e1fa66601a9ca80600
SocketDev~socket-patch~WC87AJ.dockerbuild
35.1 KB
sha256:01f194dda1e3973d350f3b26acaaa0481126f49cb573dde253144958de6ef504
SocketDev~socket-patch~WTCBLU.dockerbuild
34.9 KB
sha256:abe2f1b1286c571e0c51dc603ee1e5583c748f931889de3a1776344ee8ccca5b
SocketDev~socket-patch~WYKIMK.dockerbuild
30.4 KB
sha256:f3ec570cb3cb5b98f2137d369ca82d664386ed23f47257ff226fd53b36562690
SocketDev~socket-patch~Y6DBU6.dockerbuild
25.2 KB
sha256:53545a9c4022ba8f0bf8e406c0dab5111ea0b2697b588301393872c84d8198f9
SocketDev~socket-patch~YAWBER.dockerbuild
34.8 KB
sha256:d566de26483b4c18ae7e9bd452e8e14a8758717e972d194de30ec346a4d05adc
SocketDev~socket-patch~YI8Z8N.dockerbuild
34.4 KB
sha256:c4343eb52a6f3e8a30e4c9a860281e2383d0d5a1fbd469e44e1a5fcd5d7c4744
SocketDev~socket-patch~YUO8Q1.dockerbuild
34.8 KB
sha256:3c5ac302a29cb1d920a1b8acc02a5e9b0cdfc4a2a739de71ad5db0a5971d56a3
coverage-docker-cargo
92.2 KB
sha256:01ac04e91287ad4d161adcba04019ead6486d83dad3ffd81679a573489a5249a
coverage-docker-composer
92.2 KB
sha256:9cabdc86af02cc16caf29eac9272f0a5c2c1995a3dff085c17ea8277996e035e
coverage-docker-deno
92.2 KB
sha256:e992d9636cd559260a4cf96e96376b1c9c53d0dc9ce6bf6bc0396ed9251d80c7
coverage-docker-gem
92.2 KB
sha256:ea02ed0d9986a94718ca9cf3c0518eeff20b496e706e8b406648ce91399fc7fc
coverage-docker-golang
92.2 KB
sha256:914f5748b9b9445e9362c3b0981ad35d95c8251c6941f339834119c972c66369
coverage-docker-maven
92.2 KB
sha256:ad0daf9d58a8852a2d2b238f53f30bea8b0aeda32c0b7eaa7c1cbda75b2043c0
coverage-docker-npm
92.2 KB
sha256:b123b99406e2f8d66b4904f1777604e0560d4cd1166122a35a83976e3457ec71
coverage-docker-nuget
92.2 KB
sha256:148fa6c9d6e6bafdb39a5b5d8ca702866351ef6e7e12f935eb462cf0bb9df8ff
coverage-docker-pypi
92.2 KB
sha256:b3b31cf5c69b31f9d1c4138ca34e24d67048ae68ff3e91d9a0f9cb53754d03d2
coverage-host
311 KB
sha256:f6d656b09a2b2ff0bb069c5dc2a702744085b950ef0653d96e3d6bb7b334ec28
coverage-lcov
319 KB
sha256:40974762415dab55c7550ae51d1c9f3bc3c5af716fab9c6ad882b12d40644e10
setup-matrix-cargo
929 Bytes
sha256:f19cdf7c90391315bb0891e27143c733e67901d4a2abd798de2d7cd90f47d4fe
setup-matrix-composer
917 Bytes
sha256:1f32c45a930649639346d44508042cd70627377ebc43d7316b27b748a6c99be2
setup-matrix-deno
900 Bytes
sha256:7ed6756e1ff19af6e6efdc3624d2c19a9627dbc167e39a11ca0967191d5be65f
setup-matrix-gem
921 Bytes
sha256:2482adbb6dafc7ad554ffa5ae2ec3e9fbf67de8dadc7bddeeac545ee46b0cc3a
setup-matrix-golang
909 Bytes
sha256:b5f2ceba82261eacda96c93a45f5010a3da39f328422589078b2469791e63a82
setup-matrix-maven
918 Bytes
sha256:23abd6ad21a687b24aef450c345371d789a5e7d3076173549001a8728f921f82
setup-matrix-npm
1.76 KB
sha256:0e8fb87cf83d4f6201fd06b72035e4bf026dce335d8e107421f4a56503a879dc
setup-matrix-nuget
913 Bytes
sha256:2fe479ea97c982a3cdc395a79a8f724fdfe9780ea705360383c461169620000d
setup-matrix-pypi
1.88 KB
sha256:9586cb7c22d69e1a83c56a376bb8dd68171e7bac30d93a4c68cb75645cf2dd5a