Skip to content

refactor(cargo): patch crates in place; drop the [patch]-redirect bac… #309

refactor(cargo): patch crates in place; drop the [patch]-redirect bac…

refactor(cargo): patch crates in place; drop the [patch]-redirect bac… #309

Triggered via push June 9, 2026 20:31
Status Success
Total duration 20m 32s
Artifacts 74

ci.yml

on: push
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: setup-matrix
Matrix: e2e
coverage-merge
57s
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 (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 (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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 (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 (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 (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 (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 (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/
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 (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_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_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_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_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~1C3IYV.dockerbuild
33.6 KB
sha256:bdf67c281919373c411d96f37d2afdc198686cfd11e7373531e74bf06fdfe086
SocketDev~socket-patch~1CS4RP.dockerbuild
11.2 KB
sha256:22df38ae7540c71df1430b3b020620a47e0b8e2b2b0155ed7d78f5cdea28f8b1
SocketDev~socket-patch~21LV93.dockerbuild
33.6 KB
sha256:56d6a606e0559629eb3aaa3161c0fd1fb553bb321fbe45574f9ecff47a4843c0
SocketDev~socket-patch~42NISV.dockerbuild
23.7 KB
sha256:a38f7ba0ba01a729a7bf19232546900eb2535b3785e5e7fa243a3b2bb45c374e
SocketDev~socket-patch~4C5HSU.dockerbuild
24.2 KB
sha256:c4f0e17cd8088c043b7f2f6ed6e8be22c9484af3c6827de52c42e466b082f4e0
SocketDev~socket-patch~5YN9QR.dockerbuild
17.2 KB
sha256:95cf341091bb7f5705275d2cb6168ee6917cec5079e8fb3b7b058c672ee5ee13
SocketDev~socket-patch~6SEMRA.dockerbuild
33.5 KB
sha256:933504edeb1000f1573464e8c28ca33d802a5b43a99ffb1b5a7dcec32555765a
SocketDev~socket-patch~766EQF.dockerbuild
20.5 KB
sha256:93d21387bad755cc9e3a6834046d7ac37bbb3d5b9478a9c37fb8e28d72974e28
SocketDev~socket-patch~81IS76.dockerbuild
34.2 KB
sha256:59dcc0061bfa8233092181cd3f8172656faee665f9fcbed9e06a4da96ac118cb
SocketDev~socket-patch~8MWC5G.dockerbuild
21.5 KB
sha256:2f34305b48e238b7907fd33254c1a9f61c980a93350bc4f3e503fc4aa260556f
SocketDev~socket-patch~93BB08.dockerbuild
33.7 KB
sha256:5dac217cd710a2772e206d404e09db29edd9e8e156482dfab5d0bf553dcbd99c
SocketDev~socket-patch~94TJXW.dockerbuild
17.3 KB
sha256:fe70632d7be3c589dc901abd21c94ffd5e5aaaf4d6d22aa17d9cf527e51c5b9c
SocketDev~socket-patch~9SUN63.dockerbuild
33.6 KB
sha256:c78d0edb03c6c15590e1e4e08cd74a6b8ef8f23959940a75050c595fd89d0cfb
SocketDev~socket-patch~BFIE6N.dockerbuild
34.3 KB
sha256:865961930665e4a347bd5abb62bb2a087c87477224db0658008f3651f2a2509d
SocketDev~socket-patch~BO836F.dockerbuild
34.9 KB
sha256:55003f23d1748fa875987c2b01f6a4177e9e8f9d870b84fe5cc67ac552c1df5a
SocketDev~socket-patch~BWM15Q.dockerbuild
11 KB
sha256:afebed2d3ecfd26960443160a7af9b4427d745b8e6e4a0e5288f11ae05356f33
SocketDev~socket-patch~E144BU.dockerbuild
34.7 KB
sha256:ead48c1cc508dd9b19166377715ecb9f4439deacd6a07800f1f1c97217b9d9d3
SocketDev~socket-patch~E8VRBB.dockerbuild
33.4 KB
sha256:f1f3033be4467c51f7bff1e6a6b5544469ee28f1c39bcab796c8dc3b791cae2e
SocketDev~socket-patch~EMFFR0.dockerbuild
21.2 KB
sha256:48b10e73c09dfd0c52616d46c537736b1974adb916e25589a0351097c34ef3ec
SocketDev~socket-patch~F4LJDP.dockerbuild
33.1 KB
sha256:e42c8bf3263644af37e61f76b20f36eb22a55c1d78ae30d513a9cfd14e4e08da
SocketDev~socket-patch~F4PAI7.dockerbuild
34.5 KB
sha256:489dedcb56c0567e5416059c61aa0bf3a46a84180fdadcbd10b41e3f9aae862e
SocketDev~socket-patch~FFQK9C.dockerbuild
34.3 KB
sha256:90fbeff4568b6f71a6913f39ca21a2ad158f993dc1d8b33b0db93fa8bdbdfdf7
SocketDev~socket-patch~GEGVS9.dockerbuild
23.4 KB
sha256:6aa1f605fe8a7ce90806c8cc953a23559f46fdca6f69371cc4f30ad66282aa22
SocketDev~socket-patch~HZKEVL.dockerbuild
23.4 KB
sha256:643062a97b012567d64dc310dd4e53e02bee143f08a13d94e0cf88a50e6e2f39
SocketDev~socket-patch~J2ALJS.dockerbuild
24.1 KB
sha256:00623d537ec56ff961b4869b58195ad30999d5fc10a0d68b173f7e20a8e1335c
SocketDev~socket-patch~J4CFJ3.dockerbuild
20.8 KB
sha256:7072ba5c1164b8f327cd8d6c20c2f96b0c6f8b154c1dcab9758c048d7966367c
SocketDev~socket-patch~K6ESW1.dockerbuild
33.3 KB
sha256:ac908d127be3df643168888bd1fec755b1041708b3e8439a2864469ea9990326
SocketDev~socket-patch~KWFZDE.dockerbuild
24.3 KB
sha256:1fb90e8b2d2cfe7b4f37d18830d31106eee0e18b8260494adf4d1c063846d6fc
SocketDev~socket-patch~LC0OYK.dockerbuild
35.1 KB
sha256:5ee33d4db653901bfca805c06a12107560e408491f4c34539208c637ac51191f
SocketDev~socket-patch~LVART7.dockerbuild
33.8 KB
sha256:4458fe33c8e1aaa56fd3d3c5d6da6174fc5aeed845fa98acc634208a3a872898
SocketDev~socket-patch~MD5B6R.dockerbuild
33.4 KB
sha256:f407c9c581c658e3683e3d0c6d1b1baad62b5d489fa1ec93562236be4cd901c4
SocketDev~socket-patch~NTZ4U0.dockerbuild
21.9 KB
sha256:e29f71e12a8dfef346c38313b78f9c68240214a5673abfba60400fcc42e19146
SocketDev~socket-patch~OHYGMH.dockerbuild
33.9 KB
sha256:c3f3794c92779e10134a19d8968bc5fa282ed24b44357028174da6753cbad471
SocketDev~socket-patch~OY21FP.dockerbuild
34 KB
sha256:79e9b00c009499426906742e02c8ca886b1ecbe7c6605c2fa7407bdb8b75ca21
SocketDev~socket-patch~PZ4ST9.dockerbuild
16.1 KB
sha256:ad7292fadfc405cbb35e19c43b081604dc8bd0d783b341798274898655302b37
SocketDev~socket-patch~Q0G6RC.dockerbuild
10.9 KB
sha256:f4271a5487e8f298c28020e3454a9fc8d1a026c59bd98108eb27d76ae9aeb265
SocketDev~socket-patch~QL6CHM.dockerbuild
20.7 KB
sha256:eaca4af0d63a693c424006d0b16eaa20ff49a7e21597d432522cffcdaa2030d8
SocketDev~socket-patch~QQ3EFV.dockerbuild
34.1 KB
sha256:c698aaa9df488b1886f3effd0150eb12f6cd0d4b50d905848f6d6041bc5f28d7
SocketDev~socket-patch~R6C624.dockerbuild
22.1 KB
sha256:c63bc6eb7144a61285097c38795e6b4d99c0851b47f8eb65287105ff43795267
SocketDev~socket-patch~RJELP4.dockerbuild
34.4 KB
sha256:466942a6d89503b0d08349be2e7240fcbe125aa4fecfe165d339b4633d094b50
SocketDev~socket-patch~SL53LF.dockerbuild
21.2 KB
sha256:a139d1ddc89ef20ffd4ec4e09acfec88bb5f88b49bc55c4f43ffe0e367b8839e
SocketDev~socket-patch~TAIEFB.dockerbuild
21.9 KB
sha256:7b3118617d670e22c819fdaac94212fdb4d1519b28d0f263685cec598df21f3c
SocketDev~socket-patch~U0KSOG.dockerbuild
21.7 KB
sha256:0000b5c3796128703ef5f7257c6450d38a423340d604078799f0160644ecc28e
SocketDev~socket-patch~U625M5.dockerbuild
17.7 KB
sha256:0b0a7db7558a83303046fc92f7c3e3848a57be7abc21c7dae520e4b11851e835
SocketDev~socket-patch~UDXDGZ.dockerbuild
16.7 KB
sha256:8c0b0ffdee577094a859654614f665e4d66cb5f7823f619f4cfd592f3f34240e
SocketDev~socket-patch~UGE803.dockerbuild
33.5 KB
sha256:4c40e1298388657bc8041f0fcd42d814e92f895cb38879e08a55d57f18220e1f
SocketDev~socket-patch~UQLFIU.dockerbuild
34.8 KB
sha256:bb2e988928704f4f657a005045242c0bd31c7734d5cf95cfd7bf54b1ecaf780a
SocketDev~socket-patch~WPXNL9.dockerbuild
18.7 KB
sha256:ca32380595d825e4d47022350b3e4d0f95fc46513dec9cadc016aab502bc5ef8
SocketDev~socket-patch~X5FBIJ.dockerbuild
34 KB
sha256:317bdd7a365cb4027872d9ec6db859a0f0a991ce706b28dcaddfb682f884111d
SocketDev~socket-patch~XHN9T8.dockerbuild
19.7 KB
sha256:6c1734742b405fdcb047a250b3e8c88350aec909c40a0852774d9adb25c9de9f
SocketDev~socket-patch~XHOQKR.dockerbuild
34.9 KB
sha256:017690cedd8fd6e5e8b5d6342f4ac2102930b10a1bb5ca2adce2549b1ee4ace7
SocketDev~socket-patch~XNTS6N.dockerbuild
33.2 KB
sha256:168bd7d60948996a1c883a2a7bbfd992512aa9cf341437f03122eb1c122fb0cb
SocketDev~socket-patch~Y2S4D3.dockerbuild
33.6 KB
sha256:6b84b8a8fa5b8507c76e6b1e0d242823de11395193a212bc6ba5339333eca00a
SocketDev~socket-patch~YJZHZF.dockerbuild
21.3 KB
sha256:aa0c2a03e42233ca7ca8a90883ed5ac15ffa4e8666170188ccc2437fa8d7e84b
coverage-docker-cargo
47.1 KB
sha256:4adb734312e955dd269315a34ceb34d0021113cea800fd990217b65294f86381
coverage-docker-composer
47.1 KB
sha256:c8722835a261635f67dc1d3249a83e56b368f8a05da065c839651116b3912095
coverage-docker-deno
47.1 KB
sha256:162ab25208fd164b7003c26c851d3039ae962dec51c8275cbd601cc994c40b9e
coverage-docker-gem
47.1 KB
sha256:a5f69633409f0bc9562edd5e9619b5bf044d0670d174106f3d01fb135bbc56f1
coverage-docker-golang
47.1 KB
sha256:ca9eaabf79de9f77351d96fca9f6909386d3da962e865fce2d2c31521966b075
coverage-docker-maven
47.1 KB
sha256:f01af33d231a728b0fac5d78e843d4632ecaa86d77b3af9380870e79308ed25d
coverage-docker-npm
47.1 KB
sha256:dc76134f3db8d6d5530f612af9121c4e1198c6fd9e0a1a0b0740ce16db691407
coverage-docker-nuget
47.1 KB
sha256:3a944c9f61fe91000c20751fbe1a7e3533606acf3681b4b7b730b2c17bd24ebe
coverage-docker-pypi
47.1 KB
sha256:e2edd3de4b7155865468dd7fd1b1112c56e3ddd37f562e9a09feef29cd3355fe
coverage-host
171 KB
sha256:8e5b15aba7aab9af3e64e87a2de987e25af63c73231d821658d739b4eacae207
coverage-lcov
177 KB
sha256:1f59726f7f364f12df8c3f603d9357bca0e300c26841ed4f883c5899bfaf8a7f
setup-matrix-cargo
932 Bytes
sha256:a0644b21dea49db787e51b28bc78758d288b9bfdff26f678d5aa606f7eb99460
setup-matrix-composer
921 Bytes
sha256:2d93417bb0199aaeb0de97ec1231c77fab77ca3d228bb1fb46a4326b7b099fad
setup-matrix-deno
910 Bytes
sha256:6c8e8e4cdc5978da567e31f814dbfd1a7f2f8e8d722eabe51d6c516d2bdf683e
setup-matrix-gem
918 Bytes
sha256:a10b3dd2fb7eea8b44d2a92fea0fb249cedbac9ab7fc989547f9556b1546d8fa
setup-matrix-golang
911 Bytes
sha256:ebdf00a7677384aa52d43bd58d0bab2052fb05a15cf4180c0abd757f491f9ba6
setup-matrix-maven
918 Bytes
sha256:896b91a223bc9bd91fa74859c6840c6f2a80fc156b058f15bfd64e39367df591
setup-matrix-npm
1.76 KB
sha256:479a4dc163e95d092568e0beb7a8e7773c9ca37dab8b279e527a43c6d02587d9
setup-matrix-nuget
914 Bytes
sha256:7e56606206202cd0d5393248c8a02b5cfbb455d9baa1d2664a8387bc5a3c16a6
setup-matrix-pypi
1.88 KB
sha256:64a02e9ea51ddbf495b6b5046115edca58caceb7022d8b622280409d96e7447b