Skip to content

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

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) #256

Triggered via pull request June 2, 2026 17:11
Status Success
Total duration 13m 27s
Artifacts 72

ci.yml

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

Annotations

1 error, 38 warnings, and 3 notices
setup-matrix (deno)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: DeadlineExceeded: rust@sha256:5b9332190bb3b9ece73b810cd1f1e9f06343b294ce184bcb067f0747d7d333ea: failed to resolve source metadata for docker.io/library/rust@sha256:5b9332190bb3b9ece73b810cd1f1e9f06343b294ce184bcb067f0747d7d333ea: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/sha256:5b9332190bb3b9ece73b810cd1f1e9f06343b294ce184bcb067f0747d7d333ea": dial tcp 54.144.228.94:443: i/o timeout
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 (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 (deno)
No files were found with the provided path: report-deno.json. No artifacts will be uploaded.
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 (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 (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
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 (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 (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 (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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 (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 (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/
test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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 (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_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_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_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 (macos-latest, e2e_safety_cargo_build)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_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/
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~09QY9Z.dockerbuild
33.4 KB
sha256:2196d26860476fd6fa2be7d17039eaf85a581035143f579c6b267617725e7b1d
SocketDev~socket-patch~22O23L.dockerbuild
33.5 KB
sha256:10bc97143fb49ada1e8679ba9e69461c132c9c0936fe453db8fd931d26748014
SocketDev~socket-patch~35NND4.dockerbuild
33.5 KB
sha256:24f74b90122e2bd6e81780886f55c2bfe5ab59bd760f90b04f826a9757612d6c
SocketDev~socket-patch~3JOYNC.dockerbuild
24.5 KB
sha256:41c029431943e8b04f50e43bcf8616aae7f9e89a399edc69f239171cc70f417f
SocketDev~socket-patch~3SQUBW.dockerbuild
33.9 KB
sha256:3c99b3288cf95459afe577c5a0574e0e420ea6fa90cc4da2db6e21636bf60ef9
SocketDev~socket-patch~4ZV404.dockerbuild
18.6 KB
sha256:90664731d0b28843731ac34f5312cdd1767810bb3949b294548ed43761bff523
SocketDev~socket-patch~5RSGEB.dockerbuild
21.8 KB
sha256:8e667197d0f052c398e839a6c63c5abf78c935bce9ea60818fa61e55f9edea13
SocketDev~socket-patch~669MN2.dockerbuild
33.3 KB
sha256:7e044f617f4211f047504130dcd142dff77764f1302d2c4e42969e3d1f6628a8
SocketDev~socket-patch~6Q27LC.dockerbuild
16.8 KB
sha256:0b2350397f0f8cb55d4ba874e65bfb6a484545c1e3283309ca94a87d3b9fbc23
SocketDev~socket-patch~8NHTVH.dockerbuild
24 KB
sha256:61fa873d91c2aed1b9b2b0a4a6577d69824cd5e5801414d766a6d3fbfc177d8a
SocketDev~socket-patch~AEVTGV.dockerbuild
33.1 KB
sha256:8e4cb670b331b83b7880d1201dc249ff33bc094b3dc7fcec290f66385d985390
SocketDev~socket-patch~BG3NGN.dockerbuild
21.1 KB
sha256:4ddb3f6ae74a6bf994142a9130321fbc76adb29c1ba7d6509ba4fb50e15a3777
SocketDev~socket-patch~BK30IP.dockerbuild
22.1 KB
sha256:a3f2800d516f3cc4c20224ad66789a056fe968d17ce0f8f3f6fc5408b669215a
SocketDev~socket-patch~HYWUZM.dockerbuild
34 KB
sha256:59663176672c432f1e6a3307e8cde7d4c60aa2d1adf181553bffe30eed48eccf
SocketDev~socket-patch~IQXH0U.dockerbuild
32.9 KB
sha256:76a626d49ac1a40d3ae30c4ed6f49a90b2a6a0b445f78dfa6b990235297ca0c6
SocketDev~socket-patch~JTD7VU.dockerbuild
23.7 KB
sha256:8490843f5db1196296c8563b563f75390e0f066befa88566f0d5032a1b05f6e3
SocketDev~socket-patch~JVWD2E.dockerbuild
33.4 KB
sha256:94c8016f434e2689ff2a58bee4f6eafda898553e103e909182710871954a08c2
SocketDev~socket-patch~K502JK.dockerbuild
34.2 KB
sha256:66c7886ebec4e91ea7debe206e0e7ba1e726117b788df9bc39e1428f04c1825c
SocketDev~socket-patch~KCNX9Z.dockerbuild
33 KB
sha256:c0f4e2a755e2f4a5a2f49668bcfc3e311ca63bc5c2d1b6a975f1650e86ccec2f
SocketDev~socket-patch~KFY1RX.dockerbuild
32.9 KB
sha256:fa822264c304610729c8edc4584b0fd50759dbd5b0a19bb33cd350c17c14a4b4
SocketDev~socket-patch~KJBU4V.dockerbuild
20.9 KB
sha256:83815d4fbbfb0d5479d5acf7cafa0030c8af78016fd54cb984241b2dd10d65bb
SocketDev~socket-patch~KL8Y8I.dockerbuild
34.1 KB
sha256:9103f8a63e452ee4139d1118b1c3ce62ef765bfc1ae71cd18116850a8b740e13
SocketDev~socket-patch~LE0ARD.dockerbuild
33.2 KB
sha256:d761f0cd19ec96b3da61a776b7e267dbec17f4cf867cef5d423857f68e4be598
SocketDev~socket-patch~LHQGA5.dockerbuild
18.2 KB
sha256:d248204c88553b7ec1ff5e101e033e926d1211f34ad16c4de6ff6203ee0e2dd5
SocketDev~socket-patch~LLS4NE.dockerbuild
33.9 KB
sha256:8d55f60a6c382525d56dd13b70a09cfb96c3c3867727a3bd46fb6f1598fd4a13
SocketDev~socket-patch~LVE3YR.dockerbuild
17.6 KB
sha256:6c979d9febfc330e12be3674303e9b99ab2b369f3d73dfc576310fff5f229368
SocketDev~socket-patch~M0ZHZH.dockerbuild
10.9 KB
sha256:9f4e4ab20449a759d3f7cbc7fa7b13993c93b30269f723ed43ebd8b2686d88a1
SocketDev~socket-patch~MIQW7Z.dockerbuild
34.4 KB
sha256:07eb2e27a97972afa7a6eccdfa3c1008b1e336dcec2e893bca2e4663fab0b18d
SocketDev~socket-patch~MKWVK4.dockerbuild
21.4 KB
sha256:78fefe80ac62362db1549af037a3cb9a48c05337e3453da235d1ece84f063f54
SocketDev~socket-patch~MR2AKJ.dockerbuild
34.4 KB
sha256:dc9ad732409a3bf2477026c9a4a18f749c45bf4d667e2c4c7250fd9b25a2aee8
SocketDev~socket-patch~NE1V7L.dockerbuild
33.3 KB
sha256:1aa00f8f892cced70cc6d64d2ffea74e1265ccfb710bd3d2d36d2e9fffbe2819
SocketDev~socket-patch~OE4JBP.dockerbuild
24.6 KB
sha256:ff3a0424b7a125852b63c63d7e10c38250df3e3bba2031c14159c2d318a7be14
SocketDev~socket-patch~PHXMXH.dockerbuild
20.5 KB
sha256:4908cc6210ff08f7ca32dce8f2b2c431f3a77b49bc868805a59da3db222ef399
SocketDev~socket-patch~PO8NNC.dockerbuild
34.8 KB
sha256:c2710aaf4bea18268f9222b9ab0f5d0d7389e0899a2075a173e3aa3287dced59
SocketDev~socket-patch~Q6OJZM.dockerbuild
33.9 KB
sha256:98a5a474456f725f4b58aa481b93733c38eccbfd481879e3cd3805a8bd9cdb46
SocketDev~socket-patch~RI1BQU.dockerbuild
32.6 KB
sha256:37ade81278945dfc06e0c63e9d9d7076e8bd2e63f1e3adeb1726a4ba28b9ffa7
SocketDev~socket-patch~RT5YW8.dockerbuild
33 KB
sha256:9d1fcf61edfd8acfc7f0955c089a22db068f19cb665359cab44cda5baaab3ff4
SocketDev~socket-patch~RVYEIW.dockerbuild
23.6 KB
sha256:0aedfb943f5d8a45cc4200a752d38c6fa0a86e50ee1c3278ab43f8cd00a3e1dc
SocketDev~socket-patch~T2S0L7.dockerbuild
11.8 KB
sha256:8e7ec01c370bd351b56828e43dd666c574de4fb4650ffbd1604ecb0277684298
SocketDev~socket-patch~T9O27Z.dockerbuild
33.7 KB
sha256:22e0c07afcb140f796b4e5fd89be58d2e800a0c447d0c768f101f2df9dc833d4
SocketDev~socket-patch~TOYTEU.dockerbuild
21.6 KB
sha256:d569fb91c73f98b3444bb34fdde987724921f94a09505fb834690fb4b6f9ef46
SocketDev~socket-patch~TRM09X.dockerbuild
19.7 KB
sha256:0ca87e176980ff9e9e35bf9261a92baf0764929dafc7641a80de543d3a9c731a
SocketDev~socket-patch~UAEIOZ.dockerbuild
33.1 KB
sha256:33ba28a752358acba5a59320bf94d529cfbac8c758d88ab9e188f4eb562d9bc0
SocketDev~socket-patch~UC2CN9.dockerbuild
33 KB
sha256:d9db575ee2612a2e92897d66358ca66d6fa3ec11c9e59314967c1f0a84434388
SocketDev~socket-patch~VDYEG5.dockerbuild
33.1 KB
sha256:11f940c48f16903c86ba5232090530eb4d9fecf54522d98046e598bb070929d4
SocketDev~socket-patch~WBC28S.dockerbuild
22.3 KB
sha256:12bfbdd2d70fd75df92298620eacefd8711f59b49962ee821da5631e95eb9868
SocketDev~socket-patch~WSHX0Z.dockerbuild
18.8 KB
sha256:5bfe9cbf221ac673206f49718e75c89ed3327b2830e5ef08000c3c0f2017488b
SocketDev~socket-patch~WX2RUV.dockerbuild
10 KB
sha256:34704027fb987129caccb9d70701eca4939899e9ee5c786c94a7d03d1dd9ee5f
SocketDev~socket-patch~XQWT0K.dockerbuild
11.1 KB
sha256:aecb6b2801f867798aef3fa8126b911129067bc9d4d9b4d055d482740b23387c
SocketDev~socket-patch~Y72QXU.dockerbuild
17.3 KB
sha256:aaa90a30117f50803846d0de6ddad27b379b74dbd9ccbae899c5a44331c3de06
SocketDev~socket-patch~Y8MV5L.dockerbuild
21.1 KB
sha256:254abc00100d14c707c65242db66c9c9e02f03e3a53535aef9243b5e9fd96f6f
SocketDev~socket-patch~YGQS86.dockerbuild
23.9 KB
sha256:905c55efa9236ba0001e61c423efb0dd28e0d844f6e9ed25f948f69c76d91bd6
SocketDev~socket-patch~YVZ562.dockerbuild
20.5 KB
sha256:e2fed113034cbc58c7502957b49efa74d2f4ff734bc484b1fbf58c5b429aca95
coverage-docker-cargo
35.1 KB
sha256:6ca769a7b794fd9da9d9150f7c9a265b20f62f305aef7a22a86baf542a7ad01e
coverage-docker-composer
35.1 KB
sha256:529193ac1f93253c54a54f134b900c51d977c58a524f5b1de897ea302fdc1091
coverage-docker-deno
35.1 KB
sha256:e90c14afd0e3fcb15957b10f70efe7ca8c45664aff40a5346e419155a4ab7f58
coverage-docker-gem
35.1 KB
sha256:d3a791b77410866ea3309c23d432ee37722fea67b02ff917fb3072c88144ec52
coverage-docker-golang
35.1 KB
sha256:ad3f9a76ea5acc585ba667eb2f02ab54c1c49d1b5e8da760ef0e459a5585546d
coverage-docker-maven
35.1 KB
sha256:ebc174aebffd72efee776aa2d4bd58f74ea7e748b1dbf7324a67eafe8162c6fa
coverage-docker-npm
35.1 KB
sha256:dd2c4f331fd4e7f1e7f85b324d57f14686bcb298769f1f80ffc5b4627fbe8165
coverage-docker-nuget
35.1 KB
sha256:812f058d847abaf59e345040d06d68467756c9e9f40e1509d5c6991f480cb5e9
coverage-docker-pypi
35.1 KB
sha256:2bbf1e9fd4e1b3e66fc16cf7d30c2cef46a4b6e82cd73bb4b919f7b4500daf77
coverage-host
123 KB
sha256:5abf553e7898dcaf32e2f7d396a15fe528d4977a87d80d5f641bcdbf365109e3
coverage-lcov
128 KB
sha256:bb3484cb816e3b79ab5694f4ba8d1e6d850e31c2e42a719549d73cabd1a51584
setup-matrix-cargo
818 Bytes
sha256:7b9be99e0f36759c30e3193bb31dd7a6197fb2476a049722db858389ec1736ab
setup-matrix-composer
815 Bytes
sha256:3fad411e81242a5aca22069402dcde19932f8aed3b35c9710f4e4a9a7992ffe9
setup-matrix-gem
816 Bytes
sha256:a2c94e4b15dd39fc5ce84990033ce842f68fbcc6f791676ba9b5f874c8050d7d
setup-matrix-golang
797 Bytes
sha256:266422b0ade7b1c6b2b1bf950c99356238814df95ec50cc5779e494ade41220d
setup-matrix-maven
811 Bytes
sha256:eaca2ec7357d5a128083f736888baa44d84a55462732411676f7ed101454c056
setup-matrix-npm
1.38 KB
sha256:91d932dff3146e808af706021834f4c5c14a6a050a30f3f88e35eb7f64bcd0a9
setup-matrix-nuget
807 Bytes
sha256:7d8e0519fdc9be27a74697155a1d3910c365058f09d091d448560b87a23300b0
setup-matrix-pypi
1.51 KB
sha256:6ec70df026dcb711e8c2b7833ad2ee6a17d9f51e9983dbc49ef24cccab9a328a