Skip to content

feat: socket-patch vendor — committable vendoring of patched dependencies #314

feat: socket-patch vendor — committable vendoring of patched dependencies

feat: socket-patch vendor — committable vendoring of patched dependencies #314

Triggered via pull request June 10, 2026 18:17
Status Success
Total duration 22m 47s
Artifacts 74

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: setup-matrix
Matrix: e2e
coverage-merge
30s
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 (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 (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (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 (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/
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/
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 (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 (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 (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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/
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/
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
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-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_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_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_composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (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 (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_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~3DDTQC.dockerbuild
34.6 KB
sha256:ef62beeaab2d28ef38226721c2b665aabd13cf0cdf5c53b978e04b16da0e6ca0
SocketDev~socket-patch~4FVGVX.dockerbuild
16.5 KB
sha256:ec0a94302698aff9577dcf3bc817b7f26a36ef3a84436025d28fb4c683947f11
SocketDev~socket-patch~4PCEYQ.dockerbuild
35.1 KB
sha256:551cc0ae6fda75f62540f211ca5645b6b4f193f2e109c4e7cb833aa42607e676
SocketDev~socket-patch~4XNYCS.dockerbuild
35 KB
sha256:c5219fab762f932038441d8491bac3bf8c4be0b233ca7959c5c4eb904a4e6662
SocketDev~socket-patch~568XT7.dockerbuild
18.5 KB
sha256:12c9e78a577058a669a8d3f6dc910745e306e5085f5639446e4e8664a30b200f
SocketDev~socket-patch~6RQBU2.dockerbuild
31.1 KB
sha256:2b000ac2242d00d14982da92f57860331ba90e77fb5498a3a3d4c20c2eb40b04
SocketDev~socket-patch~9HJ971.dockerbuild
35.2 KB
sha256:7bd0859b5d1a9ccbd2112f2b13353581096d44005fb565ae62a84f3bce54eb30
SocketDev~socket-patch~C7SXXQ.dockerbuild
21.4 KB
sha256:2dea73b90f4b482b0d7bc1128004bf356b7e4d49a1b0f6f182a947f0ba85f446
SocketDev~socket-patch~ETXWKM.dockerbuild
18.8 KB
sha256:420a8cc2ad77bac1adbcfef555f14f1fd977acfc94f57bafb8a0193a814f9b81
SocketDev~socket-patch~FU0U7C.dockerbuild
34.3 KB
sha256:f7f5d71ce51c445c0f118a796ce4ab16a588dcea01f612eaabc697cfb4a6d81c
SocketDev~socket-patch~GW44K0.dockerbuild
34.6 KB
sha256:9a0d13a1b23b9ca2f8aa4ad780208a04462687854a62267ddfe52278c9bdd21d
SocketDev~socket-patch~H4H1OO.dockerbuild
34.2 KB
sha256:50d2cd8a91b9ebd32deb4a4da9ee18a48a5937f27869e07d7aac2e4fb830c6c6
SocketDev~socket-patch~HICMV4.dockerbuild
22.9 KB
sha256:0f6f9061643c492dc05e71a4d7518f465091dab8dfa77757d21f3191ee5c0a5b
SocketDev~socket-patch~I00CBL.dockerbuild
35 KB
sha256:7faf659a62f1ce5468d99af5c5443e8d7a61da6caddb9d8efe29152d5520c097
SocketDev~socket-patch~J7P2IY.dockerbuild
35.8 KB
sha256:d3188301ea3db0741a4ac81eed044413bc5fd5628ade5120106638faf0e91cb8
SocketDev~socket-patch~J9Z55G.dockerbuild
34.3 KB
sha256:96cbe8144241f83f75fa63e38e84f172239aa0cfe109735efda3570bcd22b719
SocketDev~socket-patch~JAPY5V.dockerbuild
18 KB
sha256:f1425e681f7108a6cd15ae03f4abf44e85434d7a3e437d4dfb5524c05cfe2032
SocketDev~socket-patch~JSONNE.dockerbuild
21.3 KB
sha256:2f5a70805267afbc60d67ea107f53d63bf2b6c809d71254eb3fcf43585715e98
SocketDev~socket-patch~JXD5SS.dockerbuild
34.2 KB
sha256:e0444d45977c7bdca814d7f72ac8e48fcd5f5dfabaaa1cfbddc2c5bddaa3e0cd
SocketDev~socket-patch~JZG0XF.dockerbuild
24.1 KB
sha256:f2a8d4236922720c58bf109aebaf5a0002a64d0c087f22f710b70f36cf34be92
SocketDev~socket-patch~KKUYRC.dockerbuild
21.4 KB
sha256:aec6538444b24c514c57fd1b0fec129932ffe9ab7d75a906e5fa252058ef6b1c
SocketDev~socket-patch~KS1M33.dockerbuild
24.7 KB
sha256:68a249ced473ac53a5d8258ba7ef62aaee233f6e32daab3fb4e680b6922452f4
SocketDev~socket-patch~KVPMK5.dockerbuild
24.1 KB
sha256:3c8588a67679b7de28c10bff1fddb461ed7660a528fd176817bd1bcbe3de456a
SocketDev~socket-patch~MSZ1NK.dockerbuild
35.4 KB
sha256:f28c22403663f194aba3847ba1a2cc2e34479a9f906d885955cc606c30003cb3
SocketDev~socket-patch~N3R2WE.dockerbuild
11 KB
sha256:06bab42ed8c683bca1f86f557f409e0e2ee727654608b63d13226a83cf9a566e
SocketDev~socket-patch~N45TU8.dockerbuild
24.2 KB
sha256:3a9771f35f43612cdcc0f6ac90f3394171eec23538de76b4ae496164adeb0a66
SocketDev~socket-patch~N4ATP6.dockerbuild
16.1 KB
sha256:9602cc91c1da4c71f5198e40e2c6ce368e3b5bf9a830903cb2af4c24c7a9e1f8
SocketDev~socket-patch~N4PE1V.dockerbuild
20.6 KB
sha256:5e7231dc7d62eb0fb4daa7b99a0539ef14d292fbddab786f6a8821e2d959092a
SocketDev~socket-patch~NHN6YS.dockerbuild
34.2 KB
sha256:ff8e068f7a09af629fa9ce4894b276e6994b8fd41d33e9710e794509ac29c08a
SocketDev~socket-patch~NXK86K.dockerbuild
34.4 KB
sha256:eba4a4ef7fd43b2f7de02d9831139c8930acf5c15a1e6151c2bef5cf0e867c98
SocketDev~socket-patch~PHMX67.dockerbuild
34.1 KB
sha256:e1936fa163dc128772e02a45faef35fee36cd86b04326d268fd129298e4e1a5b
SocketDev~socket-patch~PN222D.dockerbuild
21.9 KB
sha256:d418f482d8a2825e8a31c4ce78439714d1c1081402148b299aa5b4a946981897
SocketDev~socket-patch~Q2NIWB.dockerbuild
34.4 KB
sha256:0f7981034311b770001816fa016d423b14e3975502625f029e024883489ad559
SocketDev~socket-patch~QPMDZI.dockerbuild
23.9 KB
sha256:c87150b5654177332c686e947a2b7fde7c16f7ea9db8777cd2775c6d882560fb
SocketDev~socket-patch~RK1HCI.dockerbuild
35.1 KB
sha256:f1877ab62d3236e8d37542a3cc9e0fc85ea0f26a0c1134647f8b2c5147a7f4f6
SocketDev~socket-patch~RSFSRF.dockerbuild
34.4 KB
sha256:9c552953707307b62ad94c49e086ade732302c1a5c7cc2f0bece20ca14d7b091
SocketDev~socket-patch~S0JFIP.dockerbuild
20.9 KB
sha256:ccf6a2ff90317a2f91d3fda5abcbdfff95e478fd08d34d4d9ee91a9af23a1a92
SocketDev~socket-patch~SLIBS7.dockerbuild
35.3 KB
sha256:f9f8a37fac9e832921c495d6cf789644cd59960e23fcff1feb0fc6e48ee933bc
SocketDev~socket-patch~TFF9IT.dockerbuild
34.7 KB
sha256:ff3b71fca5d599d5b8faea8c0bfb6664285304093cd1e171e37dfff9d2b0bf3d
SocketDev~socket-patch~TJI9SV.dockerbuild
28.7 KB
sha256:2f03eccde2e21c027015cad11e5976d74707e74cd48d0b4da99b3a97d19b8a21
SocketDev~socket-patch~TMPGEU.dockerbuild
34.4 KB
sha256:9749f8ace9709ed076295908ed9619e621e1c4121a35b926702a6ebccc725f82
SocketDev~socket-patch~TXQGPQ.dockerbuild
20.8 KB
sha256:ec644c5f255617eb01bc7f5fbd9e12d9e09fac5d2b5e07784889d619507e744b
SocketDev~socket-patch~U1GU3E.dockerbuild
11.9 KB
sha256:bc886183e01b3a0868195fe6bedb99152f65bc55123f26d4f044628e07adc553
SocketDev~socket-patch~UEDWAI.dockerbuild
35.3 KB
sha256:181e907a5440a366a2a6ef9e366160fb28b158cf3abbd7bcee1ba872aaf05f08
SocketDev~socket-patch~UENX1C.dockerbuild
21 KB
sha256:3d138eaaacf535d7404fd2458cf3ee9b020244681c0ad652e16f0cc9a1797cda
SocketDev~socket-patch~UXN2T1.dockerbuild
34.6 KB
sha256:3ead58500fc08a452225903412ce7bf46d201730df97b8ddd4f700453204fee1
SocketDev~socket-patch~VROT14.dockerbuild
35.1 KB
sha256:84f395417ce17ba3843f2eb8fef0e3054d5ecdde8e072e8a4cc0edd5811d5081
SocketDev~socket-patch~WD491O.dockerbuild
11.7 KB
sha256:a2e9bb82da58f68624e64568304b359809356f1a19a9e62ca79d390392f327c8
SocketDev~socket-patch~WZQPP8.dockerbuild
17.6 KB
sha256:2e057c114ef4aa84a8aa5cfda4310e30c84525b474f29d613eb0bf3ebd4522e6
SocketDev~socket-patch~X6CXY5.dockerbuild
24.8 KB
sha256:598ba6c69aa209de1da16f254adf329c5a421db747df488cafb2502d697bc671
SocketDev~socket-patch~Y3W8RI.dockerbuild
34.7 KB
sha256:519df3da151c420ed4b630a2da99d11ef9ed045eb2c3c5399623860628f38d9d
SocketDev~socket-patch~YITRLD.dockerbuild
34.7 KB
sha256:42ac9664fa88953c09073e91d3824b10a85ccff18b07e02636dce52b759c4c72
SocketDev~socket-patch~YV6S4R.dockerbuild
33.9 KB
sha256:ae44d416329c44591df241cefbd7b8fbc0a013a2b9bcf827fe736802efe72b2c
SocketDev~socket-patch~ZDHY7M.dockerbuild
28.7 KB
sha256:c9c33f497bf139c0fe7c779a55e33eb3faf0c3a033951c53bb345898ccd64d58
coverage-docker-cargo
74.6 KB
sha256:a02af3609f8b2cb20f25c75751ae2f22a302d63869572ae376c718507690c8ec
coverage-docker-composer
74.6 KB
sha256:cd7831503053a77ecbfb189a629c678f5790ec18e6e32a4c5219a5058305c03a
coverage-docker-deno
74.6 KB
sha256:9063777e88078dd3baf3d0a224b8e505adff5b99aeb7bfa3ecad96a3920c7193
coverage-docker-gem
74.6 KB
sha256:9afbdd5b9412a038b9fcbc2b9cf4d98e137dcb62388deeb619c6d8da665173f3
coverage-docker-golang
74.6 KB
sha256:fa93e9aa2f2b69da8d3e9929519940020b97e196e3a52ea9f7537686fde92ac9
coverage-docker-maven
74.6 KB
sha256:90d446e677e17a6680bc030676b9cd17461a67ceed929d4d70257636fd896bf4
coverage-docker-npm
74.6 KB
sha256:87439402bd309fe85ac543f3bc59c26697451b16c382fc99d5d70bb1ba027a3f
coverage-docker-nuget
74.6 KB
sha256:9cb9a079739be57b2de21bdbc70e991d0e8a40b1cf13f380e2a9ce59ab9c69cf
coverage-docker-pypi
74.6 KB
sha256:1eea3a37cf5ac9db03b75761867f0942dff3b84d61b2d8a42121927fd76adc3c
coverage-host
345 KB
sha256:b2b55f0b0cb80140bba6ccd81d5ac0cfc5f484225c2e3d217eaad68719d1d873
coverage-lcov
350 KB
sha256:66c198218628fd0ff019c4cee3c66a916b7be27e497add068618121ac15299d3
setup-matrix-cargo
930 Bytes
sha256:ab1237141f4b38c655c5ec99c921ab3d43157ec13b25f0209e55cb565e9fb0f8
setup-matrix-composer
922 Bytes
sha256:48adfee9e7712ca8f730fdbefbbccd775396339848892164f6d8fc6f900a07ee
setup-matrix-deno
910 Bytes
sha256:ff8888f0ea9fe8f2476cd63802cb9a53d4b1f1ce5f0dc9710e66f3de8b76e044
setup-matrix-gem
925 Bytes
sha256:f5551340dffe74cebe0fcbcbea56689dcf3040c335f0088279cd4a093ca4ba08
setup-matrix-golang
910 Bytes
sha256:bf745163e20183c5aba0eac46d63aafb89bddad7342ba4ed89b6d5f7afcbd0ac
setup-matrix-maven
916 Bytes
sha256:d7d2ca3fdec0d35763a7bff85861df6de624bdddf87a5e33c702da42e075c746
setup-matrix-npm
1.75 KB
sha256:aba69f44b8719c4f97b7ba2951e6b6a7599f2b9ab21d3d8522484327b911b51f
setup-matrix-nuget
914 Bytes
sha256:51d2a443fe81c451f595391a60a379b8f11dcaa6bbc1dec72adf053dff8b6b62
setup-matrix-pypi
1.89 KB
sha256:4774c4e49ba4c2d8d3eb00074b4296b8d2a38d3a2e30229da2b55e14266fec49