Skip to content

test(setup): experimental end-to-end setup-flow matrix (all ecosystems, workspaces, monorepo) #255

test(setup): experimental end-to-end setup-flow matrix (all ecosystems, workspaces, monorepo)

test(setup): experimental end-to-end setup-flow matrix (all ecosystems, workspaces, monorepo) #255

Triggered via pull request June 2, 2026 16:50
Status Success
Total duration 11m 48s
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

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 (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 (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 (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
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/
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 (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 (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 (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 (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-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 (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/
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/
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-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_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_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_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_composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_safety_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_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-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~0LHRHB.dockerbuild
24.1 KB
sha256:5ee6f291241ca421a114273056b3ab25caf4c38880a7d86aa71c07c82037cbce
SocketDev~socket-patch~2TC5QR.dockerbuild
33.3 KB
sha256:0c801a5af4805652f8eb5e4c625b57a27bf4dc1797b3583e1f2ea6bc51be8a27
SocketDev~socket-patch~3L5RU7.dockerbuild
21.7 KB
sha256:6fcbc94cdf107a44b697ba58d1fcde00460ad8755123204c61cd81c4a3c38650
SocketDev~socket-patch~3XGVZ3.dockerbuild
18.4 KB
sha256:9cc05224a1755bb28dba6ad222b44fbb6bee770846763552ad6bbe88780d53be
SocketDev~socket-patch~683P87.dockerbuild
23.7 KB
sha256:2b5755441af34a49905fd88e253b395b8f545ec3ef29084d42890b21193e657a
SocketDev~socket-patch~6H7EX6.dockerbuild
33.2 KB
sha256:2e8380ea1d209208f8c9d9f32b46386dd5a90955488dcbb6a064f3f0a9c6c7f0
SocketDev~socket-patch~7CDG3O.dockerbuild
33.8 KB
sha256:b295a741fb6a607eab224af794e649d2f902fef6e65852f4251cd0d2fcbc656d
SocketDev~socket-patch~7JG2RO.dockerbuild
32.8 KB
sha256:6cb5a534286e9676bb4705ab43245b0d80893de30a3a43463358dec7cc4acd89
SocketDev~socket-patch~7M4QBG.dockerbuild
24.8 KB
sha256:a1418ac8e27a5436090478c078526536127f130cb3f6a6224324777aec61c191
SocketDev~socket-patch~7XUOGM.dockerbuild
18.4 KB
sha256:6876fa36d7765e1540295d1cf9bfffc930a9f2ac1063c4200fe63cb9980695f0
SocketDev~socket-patch~AW5KRV.dockerbuild
33.5 KB
sha256:fd7569ac80c4cad2b448c830a65c5c234815f6ad45593ea554639e48f4712f1d
SocketDev~socket-patch~B7B9EE.dockerbuild
24.2 KB
sha256:15e504d188014a0e365e192ef7284f23e4120e83311d764d13203eb4446a015d
SocketDev~socket-patch~BA40VH.dockerbuild
18.2 KB
sha256:8f7ab0445d604601bb7a468478e4e46d76e7ad463dd61c6eecea50b6d057abbd
SocketDev~socket-patch~BP80SM.dockerbuild
24.1 KB
sha256:a5e4fafdd8070c6567981bb4c7975385f1030e8fffc534edb9920c01388aa0c3
SocketDev~socket-patch~DJKJ56.dockerbuild
34.1 KB
sha256:175293ec87221f30280749aa89753cec41dce129c4b8016506204c6b38f273be
SocketDev~socket-patch~DZ3T4F.dockerbuild
34.5 KB
sha256:231c6651a6c7a542174584128a69de9bfd9bb0947927d6059d55056457c3a736
SocketDev~socket-patch~EV9M0R.dockerbuild
33.8 KB
sha256:17685e0bbd0450efdaebfadf3b951e5e6f310d065b70dfc31fb3e7ac30e91e0f
SocketDev~socket-patch~GJ4IEF.dockerbuild
33.5 KB
sha256:637436485617be7c18d46d5556f91167fff991d8e53c723e9ecb6bf85e459fba
SocketDev~socket-patch~HEHK1O.dockerbuild
33.2 KB
sha256:75480d71c80a9333dda5e0c7a34fb809a829af6e55d3d3b9164dc5efbdfe8696
SocketDev~socket-patch~I97RHN.dockerbuild
20.2 KB
sha256:01a3d0edf4de10dba2663094e8de1a88a5a0a75ced7dbf80110789e5611fbe42
SocketDev~socket-patch~JYVT86.dockerbuild
32.9 KB
sha256:73ece53b2d104d30d4f39b4acac1820c04abf2eb6bef15c898a134d6c56a73a1
SocketDev~socket-patch~K04FIY.dockerbuild
32.8 KB
sha256:3a3a1bb5a4a9683016ebe068ffc7f3727c24da560a4f247e6e584500a36d9a5b
SocketDev~socket-patch~K5NXNC.dockerbuild
16.5 KB
sha256:bbcf87bf37e8fe5c1da8310228d1ae8ffa1c688c1d657cdd35cb31babb014d38
SocketDev~socket-patch~K7O7AS.dockerbuild
16 KB
sha256:956bf0e3d8e229e6e7450a828f4a284c06281da1b661f83a82c36bbee63718c7
SocketDev~socket-patch~LFE8AW.dockerbuild
34.5 KB
sha256:dfbf9e51e286bcfe4c9ed5577e0da5128e7ead6ac7ad7a9ddaefd21b6a746c5f
SocketDev~socket-patch~LPZ5E4.dockerbuild
34 KB
sha256:254ade10f98e879a3893c4d2d810609ca666648210eba39b2cf4d84609b97c21
SocketDev~socket-patch~LYSB1X.dockerbuild
17.9 KB
sha256:9d193cca94240bc585d5aade124874438497375a89fda9f6c1d8562ed2fab2d3
SocketDev~socket-patch~M02TTW.dockerbuild
33.6 KB
sha256:967d779a8fe62d9b90686ba7629b480cecf807396006f196d68ca4aae5e37bec
SocketDev~socket-patch~MJE65W.dockerbuild
32.4 KB
sha256:bafffd1a451a8409895d71764762be23fd65d5221a0555e982af162d511bc855
SocketDev~socket-patch~N6W7EI.dockerbuild
21.5 KB
sha256:93ee58c98a157cb132404f46f76eb664e3482f217c670918c08ce2be519f19cd
SocketDev~socket-patch~OGGJWS.dockerbuild
21.1 KB
sha256:4d8b4c6f23c6b9da44bd4be28bd95143cf68772b42f477c80f27ea25705e521d
SocketDev~socket-patch~PF5JI9.dockerbuild
20.5 KB
sha256:ec206040b00d882a5012baae2abe285e8c723dce10c186acde58b963c721f809
SocketDev~socket-patch~PSA37Y.dockerbuild
33.7 KB
sha256:08f39d85d41223c4eca474a14590048bd27e0d568a7704a9c81040acaa7365ca
SocketDev~socket-patch~QC3I5Y.dockerbuild
33.3 KB
sha256:48a79145f6ade05971bd69f5c16a4ce80d095fa7617c5d88b45321ed8d67aa06
SocketDev~socket-patch~QH8FE1.dockerbuild
20.4 KB
sha256:cc1bdec7381b119937b60216a9080bc7fe956cb086521d134c332ed0a8feb02b
SocketDev~socket-patch~RTPI37.dockerbuild
21.8 KB
sha256:e435742ea69ec79f260b11f624dce39b92f9fc4caeaabf0343b272d463a20a78
SocketDev~socket-patch~RTXTCG.dockerbuild
34.2 KB
sha256:f084a7a3f3e399120620baafd7733cfc25dc9b7f5e5a6c67fe34b011178e7af9
SocketDev~socket-patch~SFJPTT.dockerbuild
32.8 KB
sha256:beb50922ec3b7b3354504527c576e4ee16b5ae32c42710a58001b24fdcd7d880
SocketDev~socket-patch~SP3F6V.dockerbuild
33.2 KB
sha256:c16f624c0eb370efd56e593b80ba2e06866b595eac58ecb7cb9e494ad032fede
SocketDev~socket-patch~SRUSYK.dockerbuild
22.1 KB
sha256:4f0a16c9739bb3ded2568b09c0e932cf5376cda45bce38f368f9d63e1556607d
SocketDev~socket-patch~TNWPNS.dockerbuild
33.3 KB
sha256:4d87cb26bc211cce4ba0a5b86f1dc5033b7895995ad9689dbdce3380f51b3075
SocketDev~socket-patch~TWF0CD.dockerbuild
23.5 KB
sha256:b22b2171bd3faf21f8ddca845bb13988502b3fb4ac7b41975212c4f9ad9abd5a
SocketDev~socket-patch~TY93KG.dockerbuild
33.6 KB
sha256:bdd5d15902f5eeea767656fd9be1ccb2ba4c03a145bd96413a765e8925491771
SocketDev~socket-patch~U08YZH.dockerbuild
10.9 KB
sha256:314de86fe9e8d2a8037c10d787d0cccbc57adb3a73c3fd4be4a451e1bdb8c12a
SocketDev~socket-patch~UE6DH8.dockerbuild
11 KB
sha256:16a84c0ede6bd0d08ce6918c2c94027471f17b1024b70f62c590c656ec5a488b
SocketDev~socket-patch~V9EL3B.dockerbuild
20.6 KB
sha256:0f4d786fd89c80681292f9faf876a42b14573da1f5bbf0f9350a0d8fea4121df
SocketDev~socket-patch~W6U781.dockerbuild
33.8 KB
sha256:67cffb1cf3404f7efbfeda6b614f104bcf0765d8e8969647959121606543abae
SocketDev~socket-patch~WNEPW4.dockerbuild
34.1 KB
sha256:4af97483cd30d1d0f37ba2ff2a8a1d50cb8f9b9f78e126fa521ce07ee246f59b
SocketDev~socket-patch~X9W9PS.dockerbuild
20 KB
sha256:05ac1146e97528a1076c614e69bef7c1acdab1ab5327c26330da1ba47ab4fdfc
SocketDev~socket-patch~XRXCL9.dockerbuild
20.8 KB
sha256:59de9b3362c59779e0b390183c573cfab4612908478e5eaa3771366b1fedd522
SocketDev~socket-patch~YLWJSS.dockerbuild
33.1 KB
sha256:fcbae7428012cc450b9b34fe0c1f2056525a052041f1ce48e7553c767f7ea177
SocketDev~socket-patch~Z748BP.dockerbuild
11.1 KB
sha256:673f3bf2890e6e8ead9a09f2f1a5cc7e606e417dd0668eff7f9ff8ca44641b81
SocketDev~socket-patch~ZKGHZR.dockerbuild
35 KB
sha256:3350ff2069a2ad2beda33a38b3f3d7d32c534fb8ddc5a46d03a3bfbc818ff0bd
SocketDev~socket-patch~ZKIGCU.dockerbuild
21.7 KB
sha256:0a407cca9778e18a9b204b9357c1a55c56bdc3f6bbc8dfad592a386d2b0f8442
coverage-docker-cargo
35.1 KB
sha256:18cbfdaf167b04c2f9df9d7a72ca0c08b0610ebf1f40d61aed15c6e98e2e84b9
coverage-docker-composer
35.1 KB
sha256:a5c506027553b125ed8103848adc367b21f1e525a610c4521659936f523b0ab9
coverage-docker-deno
35.1 KB
sha256:e87cb215b21321638e0a29e073d4526c8f05dc459051debbdc825b6549df1735
coverage-docker-gem
35.1 KB
sha256:d6dde59655b59f1e9f9199a9e566ffafa08f3485b2f83f12d20a852ed5d700a7
coverage-docker-golang
35.1 KB
sha256:fe7201d22cf88c768872505076eb56e9a4c8e21570807d688e70f4b72953fbb1
coverage-docker-maven
35.1 KB
sha256:887f4f27cf23638b56ba46ba90a2326b412b12e54adcd9aeae7d786430a57449
coverage-docker-npm
35.1 KB
sha256:8407cabb0f59dd842ee536a2faf1494fb6c60d9710ce3f145972356b8914b3b9
coverage-docker-nuget
35.1 KB
sha256:84f5016922a6275e9a4e362c60f30303867f61a351249613be20a7d24f3f5614
coverage-docker-pypi
35.1 KB
sha256:241f4e25d7efd3a33796870dd948d18023a0b2fb7b645a79c60c43524de8d0eb
coverage-host
123 KB
sha256:8baf6311529dd28f3f95fc7f6461789086b163c92790add56375f6ce3b15a546
coverage-lcov
128 KB
sha256:50023a7ed2dedb334483ab77d4a61ddcd250b8e61bde588cf59257df28e24f0c
setup-matrix-cargo
790 Bytes
sha256:ab065438fc8828c388ad77b057f2178960ff2d3056967ca1e5b56c9dad5737db
setup-matrix-composer
784 Bytes
sha256:b7d2f167407f5c2bc0a8197c6b9dda5d3dda550426240bcc7bc5c733a98e974d
setup-matrix-deno
772 Bytes
sha256:6dcd3b14f16578db6ad5ecfefbf31e9c2b074a9029ceabbb5aae60f5ebddfdde
setup-matrix-gem
786 Bytes
sha256:d3da9cf84468226cd1d11ddc997faf9d7808ca022724ad8d2cc1347870f45555
setup-matrix-golang
773 Bytes
sha256:6ab153d0b2e4aac94c1d14b6660ed076c384844b6c623d7b4c51999642f37f34
setup-matrix-maven
784 Bytes
sha256:f73a678afaaf5b639c0fed01eecf48bc3595a8daa969a8d2353a80da464eec9f
setup-matrix-npm
1.15 KB
sha256:d843a0106cf93ab266964a8dab7a0d88a6f360db466e92d3bffeecaa63cc00ad
setup-matrix-nuget
780 Bytes
sha256:9286f2eb5c5ab237090d76bd42cd5df4551f353ace5200df619a1a00f690d936
setup-matrix-pypi
1.33 KB
sha256:50558a7b2c8a42f7297df052ffcc4aeed19b3cae812fa8d999efeeb78dbca006