Skip to content

refactor(cargo): patch crates in place; drop the [patch]-redirect backend + build guard #306

refactor(cargo): patch crates in place; drop the [patch]-redirect backend + build guard

refactor(cargo): patch crates in place; drop the [patch]-redirect backend + build guard #306

Triggered via pull request June 9, 2026 13:47
Status Success
Total duration 16m 55s
Artifacts 74

ci.yml

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

Annotations

38 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 (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 (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 (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 (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/
setup-matrix (maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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-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 (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 (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/
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/
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 (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, guard_build_integration)
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_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_golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_safety_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 (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 (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 (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 (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-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)
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~0FMQY8.dockerbuild
21.2 KB
sha256:b3c70a75b2d371c0ec77f126a413f6ec836e7681994cc9d85c3806bbfeda59b2
SocketDev~socket-patch~1IG9X3.dockerbuild
34 KB
sha256:293d163e9d9c7a23884e7d3ba5f72fd593d615ef6805dc6401c1df37a0dba530
SocketDev~socket-patch~1VQM9Z.dockerbuild
34.3 KB
sha256:d34ed71696ff96b8539116d24d5c4488e2166e8d51d7b25ade64c3ace92f474c
SocketDev~socket-patch~29GKXE.dockerbuild
12 KB
sha256:9f75ea922562aee27769b6dfbf134270eba1f71bd750b6b95eb04dabda341bdc
SocketDev~socket-patch~412JL4.dockerbuild
21.7 KB
sha256:e0fc62bd7c9a11ad21e134af9e0d45f4a141626476e97c7e503ccafac39a95ec
SocketDev~socket-patch~5D03GA.dockerbuild
22.2 KB
sha256:46b2305c345ca512c11bdf72d4f4b6371205e619af4a632c5a3872f834ecb0e5
SocketDev~socket-patch~5MP8XD.dockerbuild
17.8 KB
sha256:3adb18290b5a5998edccb8b238711fbe6413f47233ca2b0d6e596c06e1da643b
SocketDev~socket-patch~65X7HS.dockerbuild
33.7 KB
sha256:c0383dce00ce609137e3d659d4db2f9551278e1ac19504ee00149c61b594f1da
SocketDev~socket-patch~6RL7V9.dockerbuild
21.3 KB
sha256:70f50a6e13d28d9e3ee9bab076c91e528aeb5c4259dd5997313f7d16262e6f51
SocketDev~socket-patch~7CDH8O.dockerbuild
34.4 KB
sha256:23b331321b35b29b2252a5cc7c95d47976f6e9c74b4607dda483fbf78ca5f146
SocketDev~socket-patch~7UPVEF.dockerbuild
33.5 KB
sha256:ee9b3f07e4cb005de276f52022005c0fd00368ae396ca3402aae341e407a5d46
SocketDev~socket-patch~92PIHM.dockerbuild
23.8 KB
sha256:d5361074b8136da69e5858abdfac01af84e6e72ad47d098aee778dbcf5f06761
SocketDev~socket-patch~9T1VU2.dockerbuild
33.6 KB
sha256:f1dabe5c2dd2353b167f8e3719f0cab8caa7c51ba98952f4e10171353528231d
SocketDev~socket-patch~B85S64.dockerbuild
11.8 KB
sha256:3e57696177444d5f01f39470f26430eb1ef46de8e051c349942b898a4fdb1be4
SocketDev~socket-patch~BSUGJK.dockerbuild
16.9 KB
sha256:f4952cdf40601f8efd701e4b7fe5521e9833c14f191b63bc0ac430784233151d
SocketDev~socket-patch~E0T1K3.dockerbuild
34.4 KB
sha256:479e051d0f2d101238be0ce48cf5d56f89c06a068488fd7998f9c25dfa807f96
SocketDev~socket-patch~FG6JFM.dockerbuild
33.1 KB
sha256:13a70cf8b784cbe7744d9ce4bce078ac1c2222f3e014d578b4bc534bd0b927bf
SocketDev~socket-patch~GN041S.dockerbuild
34.9 KB
sha256:37663271a0ea747d9da327e42a1378a10ca634980a33dda669aec49865cb6bdc
SocketDev~socket-patch~HMS71M.dockerbuild
11.6 KB
sha256:0b74a736895bbe5c0b57b520e566b1f03192769f3e7c7b183c132b9f7f9de3d7
SocketDev~socket-patch~HOQLRL.dockerbuild
22.4 KB
sha256:b888b63b141809b844722a1630417bb3448cbc3b8a4dd9638775335cc6c1910d
SocketDev~socket-patch~IVVZN6.dockerbuild
33.7 KB
sha256:857594e8d696629d5ecad47962f4ca31532e2c6c2b7eb4b1c02cdcae876ef4a1
SocketDev~socket-patch~J9VZ5F.dockerbuild
34.4 KB
sha256:596aa0baf3a5ec5062f9b0b72363182832036f49dd274291cb639b0c3a36dec2
SocketDev~socket-patch~JBW6K7.dockerbuild
22.2 KB
sha256:808835913fc25a309e0c079aa935a8a2fef94f0cb64ade4626e6872044b7a0e1
SocketDev~socket-patch~JCI0H0.dockerbuild
24.5 KB
sha256:d540bb3e43e505b5e124aff2002a09b970a36a2c68f990070edce5404b188829
SocketDev~socket-patch~JHOFM5.dockerbuild
34 KB
sha256:07131306c25638591909084353fa6a0f5648e8d6cebde1da3197280c87252196
SocketDev~socket-patch~L9X8BE.dockerbuild
17.1 KB
sha256:37133cbf4102751933afedfa5e82970096eaaf7f8caad35d2a695f488de5852f
SocketDev~socket-patch~LECZ2G.dockerbuild
34.5 KB
sha256:2837c535204bb5823e19f38b56ee4ac091af52d917b36b7d7f02bf1f66927e3e
SocketDev~socket-patch~M5TLJP.dockerbuild
33.4 KB
sha256:ecf51b68a1d27be0f535ed7c0777d809158812168da936377e82808270028f72
SocketDev~socket-patch~MKPNFO.dockerbuild
33.4 KB
sha256:f28fe2e0c02507974dca9d528a6e1390a8a70be2eca0a9ef547c5014dbce8aaf
SocketDev~socket-patch~MLJWOO.dockerbuild
16.6 KB
sha256:be51b634d7ab277f6f53d4c5222d666710ee3e9d757d9d646d75233d332c6804
SocketDev~socket-patch~ODCV6Q.dockerbuild
33.5 KB
sha256:cfbce1f53a85bb9dd43babb4e6242eb8d1604b0a081ad8ef57b1f6194f798017
SocketDev~socket-patch~P4OT02.dockerbuild
33.7 KB
sha256:d82ec9d26ac6cfda8e1908615cdd977fdda35ffbc4f661e1d378ba1e1a7d15e6
SocketDev~socket-patch~Q9PGMZ.dockerbuild
23.6 KB
sha256:37443dfe9ea778deab32aea18df1039e055d42d7025ee383ea482a55ffadbb54
SocketDev~socket-patch~QNXOJJ.dockerbuild
23.4 KB
sha256:edcb5e655a85de10db24f5923f8709028626af2a60945763eec19a7e7aacdbe6
SocketDev~socket-patch~QOHYR7.dockerbuild
21 KB
sha256:540dda38083d31a5d707cf3c483391918ab851c77aeb9a6e16c153628096e887
SocketDev~socket-patch~RH04GP.dockerbuild
33.4 KB
sha256:6fa723baf34cea337a2d98c9abb0ea684b2ee68b8075cebb085cf8b776477850
SocketDev~socket-patch~RREV4B.dockerbuild
34 KB
sha256:d32e74a279d4f05149ee1b9f0b918300869d2f29c2cabb021c201c1fbf05363b
SocketDev~socket-patch~S3W0IU.dockerbuild
18.7 KB
sha256:d372b5a3553f143500c927eab9bb1154b5f0cb436c84aa00aaca09204d85db86
SocketDev~socket-patch~SDKI4R.dockerbuild
33.8 KB
sha256:95956468f750b763973931c8f1bc4c9e987c98fbdb9d97b42fd71d36d8d0069b
SocketDev~socket-patch~SQJCSF.dockerbuild
17.8 KB
sha256:09ed4f04cbeb7a4b2cff415849b6a4318af2bb2b654d9f6ffb00cb1145766e03
SocketDev~socket-patch~T8XEZ2.dockerbuild
21.6 KB
sha256:1295bedacbc23bf8c2b68a507da95f8ccdcafdbf130cc8b3d0a4bbc2b0973b66
SocketDev~socket-patch~TGLO2V.dockerbuild
23.6 KB
sha256:779dba6b36844eb9171e96db592d440291aad2b8feab7e7713301bcb1c343705
SocketDev~socket-patch~TU79JC.dockerbuild
33.9 KB
sha256:3c4060e6252bf4826b8d623b8a05970ff88f7465aa35e87d48baea7e38b077b1
SocketDev~socket-patch~TY0PC1.dockerbuild
34.3 KB
sha256:86a5ef26112a79852adbacf3d1b7f32487bf0fa0c7846c4ed306adda7f83dd58
SocketDev~socket-patch~U75RX8.dockerbuild
19.5 KB
sha256:689510ac63930627eed36f0dd5b4d9be4e7faa73a11e38e260ef8fd2d3961341
SocketDev~socket-patch~U84SP4.dockerbuild
34.2 KB
sha256:51c731c1e3c84018a11fc763bbad0c81498bff7c74326ef9bb5a757bc000bbd8
SocketDev~socket-patch~UJSP1E.dockerbuild
34.7 KB
sha256:c502b29c4d603d673d53543f19beb881ae97bd0dfe1e10ea28ab6984aa97ec82
SocketDev~socket-patch~UZ305L.dockerbuild
21.4 KB
sha256:2facf6e1b8405311056cd18825d6aba4faaa9620f819c955ebda04bb97980fc4
SocketDev~socket-patch~W92NRB.dockerbuild
34.2 KB
sha256:86939768e4e74c1c7e63a59240add069299c72083368b1080fa34e28c1bc37e8
SocketDev~socket-patch~X33SHE.dockerbuild
34.4 KB
sha256:898ba365af0f67bad56d9b1cdbf17c509f0de36d3bcf1f16949fb5ed85ce6ca8
SocketDev~socket-patch~X9ZBQI.dockerbuild
33.4 KB
sha256:c653b518bfaf188e9468dd121921c7988e6a057acc1a06d76dffb0fb4ff1d0b8
SocketDev~socket-patch~XS8UD0.dockerbuild
24.2 KB
sha256:301c4ca6bd6e054851b8bd745ab995d23796e1b8698b4f29dbff52644b88b7bf
SocketDev~socket-patch~XZL3VQ.dockerbuild
20.9 KB
sha256:27a1b3a7646b624407dc8876f2796ea27ba081f16ce50d05ed8af1059e9458be
SocketDev~socket-patch~YUEA37.dockerbuild
19.5 KB
sha256:a35e88c0244db0b993cead076922f10d327c8a5e180d379ef11f963bd72eebef
coverage-docker-cargo
47.1 KB
sha256:96f0371713018f1703b422c255249bd75b3f7a102b1ac2bd0c0a4b2f57461a33
coverage-docker-composer
47.1 KB
sha256:91c27bf250b12afe8a2c66b66b43fe47f4634e41d3688ac4852a53187cca8108
coverage-docker-deno
47.1 KB
sha256:60aa648213fca8ebbe92249972efbcac8e2092b3b17d03eddd17073197e91f8c
coverage-docker-gem
47.1 KB
sha256:8415bbb682fcd70cde21d3ab7d354c86f8fdcc4a2263076dcfe4608dae5feaa7
coverage-docker-golang
47.1 KB
sha256:fb094c973865fad0af1cb5dbd77c4ec93e922d98be845e335b13f37d8f2d1079
coverage-docker-maven
47.1 KB
sha256:1c2e6586a7f4865dc29a046ad7ab40b4161ec19ab902dce96537d1a7d0d24c31
coverage-docker-npm
47.1 KB
sha256:663c7c6e484cd2851cfbacf9327cef7171c43f69b1a17093a1d431bfb2b940db
coverage-docker-nuget
47.1 KB
sha256:c881a52d32f946eea1e72b3173debfdde0b1155435f7e8479b6be38790dd2ce3
coverage-docker-pypi
47.1 KB
sha256:7f3f9b63e70ef767a78893f64dcd7f6dbff7a8be351bebf4ca13150379cbd698
coverage-host
172 KB
sha256:83d6761378ccc08cd44d2f5c849f870547db36d883f828a4f372427be035d721
coverage-lcov
178 KB
sha256:c4f9dde94ad4e59fcee9d71a8fe2b20fcf0295577edb112441d97c5a670a48f3
setup-matrix-cargo
929 Bytes
sha256:7766778cae95c9da429050ec1b98e1293f071e0ea955892b54de706ffaaa9e4c
setup-matrix-composer
924 Bytes
sha256:a81eaa105c58d706ace9e1dd68668ce3cf2df0c2b8798d72de1764ee21cd33b5
setup-matrix-deno
909 Bytes
sha256:79eed52f757b235cd88ab834f80275a92bf153210c0dbf917449bf1b2e2c2607
setup-matrix-gem
920 Bytes
sha256:b403e7ec442834faf313f500d6bd5887786c4baac024967b573d8e97f2900e05
setup-matrix-golang
909 Bytes
sha256:e2af4fbe7d8e14cf42a8031fb875cd641bae983ef944ace036152b8bf78516b3
setup-matrix-maven
916 Bytes
sha256:552d139abad420f4e8db7e163a8fa90c3bd543703f4482a0e7ca6ff3287639cb
setup-matrix-npm
1.76 KB
sha256:cfa92d0f86b9d4d4cf66ed09a37173b9def81d3c0a675b44c4b634a7bea7d498
setup-matrix-nuget
914 Bytes
sha256:9d0f96b67c75d7d52992d9447ec8254850838a702b75784baa8b98fd21ad0d89
setup-matrix-pypi
1.88 KB
sha256:4c6a049b78f7f7e4e1298bb4c657bb1381d0b841e792c91f8c82367844ab31ee