Skip to content

feat(setup): add --check and --remove flags with dry-run + edit previ… #263

feat(setup): add --check and --remove flags with dry-run + edit previ…

feat(setup): add --check and --remove flags with dry-run + edit previ… #263

Triggered via push June 2, 2026 21:14
Status Failure
Total duration 12m 6s
Artifacts 71

ci.yml

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

Annotations

1 error, 35 warnings, and 3 notices
coverage-docker (gem)
buildx failed with: ERROR: failed to build: failed to solve: debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to resolve source metadata for docker.io/library/debian@sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb": dial tcp 18.235.97.30: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 (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (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 (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/
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 (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
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 (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 (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 (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 (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/
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 (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 (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 (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (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_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_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_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_pnpm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (macos-latest, e2e_safety_pnpm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (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/
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 (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~1TX18Z.dockerbuild
33.2 KB
sha256:a09ca4fd5275c3a6d2eaeeab5be6d02b1bd6c4b2376dacb00159dc700309981e
SocketDev~socket-patch~2C30PW.dockerbuild
19.4 KB
sha256:16393ca0b005ee3ee4fb15fcbc734f0125319d74b26e95fc856fc65f7582983d
SocketDev~socket-patch~4BBIOQ.dockerbuild
18.5 KB
sha256:c04c01c392433007216e51e63cbfd6aa07124a9c056a5ca70a20d1ae10b64143
SocketDev~socket-patch~4WVJV7.dockerbuild
33.8 KB
sha256:89767c9848d4d50c654bebf8d7ce3a136ee208317a86537abd844c50daf2bcb2
SocketDev~socket-patch~6OPCTY.dockerbuild
33.8 KB
sha256:4f9c8270432fe78df0d0b99d1ec6bf82b9393aafdeef5dd4ac91a1b745677964
SocketDev~socket-patch~8L8TEN.dockerbuild
20.9 KB
sha256:35f36ef672a2241cfb8ad34ae921fa84993c5bf28ca585b0581e8f3904f72815
SocketDev~socket-patch~95E6TV.dockerbuild
21.6 KB
sha256:650ffb255c4dcdc5989e491fac4cdac0d7f918437005128e6aae46c1eceab68c
SocketDev~socket-patch~9PAHI6.dockerbuild
32.8 KB
sha256:061639ee8da0b1ff509305beea645ac9c9dcec31c3fef1cfa79f9f9835a7065a
SocketDev~socket-patch~A3IS6V.dockerbuild
34.2 KB
sha256:b46d95057d0f2cd8f8c999309299e30735c09c5dc1b1158ef19ccdf4b36a8fae
SocketDev~socket-patch~AQ7G4M.dockerbuild
33.6 KB
sha256:4dcf634de7bc12758d4b4893dffef3536c0c926c511b996532857c0ef3d27b1d
SocketDev~socket-patch~BBZVIJ.dockerbuild
21.5 KB
sha256:37f240da7bbc27a5efa32bac675829f640cec2e5995034c35190a3822878a4d9
SocketDev~socket-patch~BZNTC8.dockerbuild
24.6 KB
sha256:aa118ecf5b97318d7c4f18ed425935e113304c4eb1991b82812af99fc82f9a56
SocketDev~socket-patch~C4T9BJ.dockerbuild
17.8 KB
sha256:6c2341c399a57c332cad137ed422b24daa220c7b931fecb9de75b2c59a404735
SocketDev~socket-patch~ETRZ7X.dockerbuild
34.4 KB
sha256:39b71a0f1417d231bf3cc37d09087c1dc612e9c8c5cf210da704112f45ecc7bb
SocketDev~socket-patch~HLSMA7.dockerbuild
33.6 KB
sha256:63cfd058dfffa49028f3521240c203a5ba2d4a72d90a996b77c3f165ed5194b2
SocketDev~socket-patch~IB8J1H.dockerbuild
34.2 KB
sha256:446d181e1915aa4168ecd1d9b236b425366e00ed6165ba1fb594e2bf562a1bc8
SocketDev~socket-patch~J73F91.dockerbuild
34.2 KB
sha256:08820e30736463044183a1c2881613361a1c6bbbd51b55d34d41fe30750c8c52
SocketDev~socket-patch~JEVM7C.dockerbuild
33.5 KB
sha256:ad344353a71beafd59d4544bee17629f8f0f22404f583aab160a39b991516326
SocketDev~socket-patch~K6W22L.dockerbuild
24 KB
sha256:195e77865b9b5b6460ab3e0312d2aabbe82433e3967ff2e56ed6a97955a1941f
SocketDev~socket-patch~K7OB41.dockerbuild
33.8 KB
sha256:b289e710fd4c95f3cab08574ede1a9197e5b49bcd08c6aa0a9cc300d3fa801a1
SocketDev~socket-patch~KPJYHE.dockerbuild
33.1 KB
sha256:8c9ddf3da02e88d418403bd3b0d8f6e984554cff1dc51ee03922be2337f4d367
SocketDev~socket-patch~KQSBR1.dockerbuild
34.4 KB
sha256:25b75ba8ec7bb5d26d54d99f1ec3d85efa87d9e96d5c601fc767a09b0c3c83c1
SocketDev~socket-patch~KU6PAM.dockerbuild
10.8 KB
sha256:474e641b7827544edc41bcf590dcfb278d3732215e468d3c049fc1b3c14b4e14
SocketDev~socket-patch~L8IY5Y.dockerbuild
32.8 KB
sha256:5a5991a643bcc05f134a6baa7c0f2a180ac44ffb05db89b4c8fa80db00e1ae68
SocketDev~socket-patch~LN329N.dockerbuild
33.4 KB
sha256:2cfc07e89e229ee5fe473dc49ed8962f496e6d2df555fb39aedda6c37a0aed9e
SocketDev~socket-patch~LO8A6R.dockerbuild
23.6 KB
sha256:e8924fbdd4261f496b7cb47ed0913c0383d40608d6028f00eeb89c12578378b9
SocketDev~socket-patch~M7SHHJ.dockerbuild
21.9 KB
sha256:0ea4cf21124ff21e7c6c8fa9172f74a16fd173bc494e47d6fa853d5c7ed71520
SocketDev~socket-patch~MAQB1B.dockerbuild
34.2 KB
sha256:54d66aefa5f91532b608ebbce3960568aaab1499bb800dfe5bd793dbe3f5c665
SocketDev~socket-patch~MFVS6D.dockerbuild
23.3 KB
sha256:a6d7057ccb3f553fbc71d9b9264fa9940b856dbc3e61e0173f559959e8850b76
SocketDev~socket-patch~MZ1BP6.dockerbuild
24.1 KB
sha256:f67c4a2bb27b973b9563926f9b2de14dc1d7be5182b77212b9eb6970d98959ab
SocketDev~socket-patch~MZ2Q8L.dockerbuild
19.6 KB
sha256:476627551c99ec3e0275b30f80795a0d3935a980689b7377b241538eff36f99d
SocketDev~socket-patch~N3D7U2.dockerbuild
22.5 KB
sha256:30bbeecf40c43c883fd0c714129cbcfd97ff25c858b19b0d80c420a843617d82
SocketDev~socket-patch~N6HHAV.dockerbuild
11.8 KB
sha256:326eb63a8dc080f7cc208b9c4df7bef93f0b236c36d7315ca3dabf56fd290e5a
SocketDev~socket-patch~P0P9FU.dockerbuild
9.58 KB
sha256:fb7a16ad17260a3c257b94329f45f41f1438fd55847ca91a94d2bf51bde8a468
SocketDev~socket-patch~Q7W8JF.dockerbuild
11.3 KB
sha256:aaa5592ea1e9e1cc8080a7f8a65af6c874f331f7e75db886aa592d4bf7f8a99f
SocketDev~socket-patch~R174MA.dockerbuild
33.3 KB
sha256:abe4dd6fcbccd54c1d429679728d0d7212803fbefbfbca3fba6ceafe2ae70f76
SocketDev~socket-patch~S4YYFF.dockerbuild
18.4 KB
sha256:f35435ed3857871263cc53884f916fb09043ad18e23a3a64266bf47df82285b2
SocketDev~socket-patch~S99NYC.dockerbuild
33.8 KB
sha256:9bfa8cfc85fe202bdb62f4b37a8859f878772393e283bf5b964cb5ba9aba6992
SocketDev~socket-patch~SH1S3H.dockerbuild
22.5 KB
sha256:c31dc0361be5908a0475792d70473b2d3ffee4cd96824348793f2ec7afb7f6ef
SocketDev~socket-patch~SIJRRN.dockerbuild
33 KB
sha256:fb26d92fafe381b81fa784f3a9ec4c3ae3c338da734bad138accc2236ba01bf9
SocketDev~socket-patch~SRMNBN.dockerbuild
22.5 KB
sha256:73d33e0c72ea7a80105a3e25bbaee103bb8811f9063410d9a06e8613df5d5f95
SocketDev~socket-patch~SZ9V1I.dockerbuild
32.7 KB
sha256:a74045ebb2c8d9cd5a4e390b53f071ce32bed37af53412dc11c096953233f675
SocketDev~socket-patch~TAOJS3.dockerbuild
16.9 KB
sha256:141361a552005be0d5ef06cfbae148555e73b5207f1fb38b1bb8f88f706ab32b
SocketDev~socket-patch~TDO6XD.dockerbuild
34.2 KB
sha256:3d8ac5d750df3ef6b1a81b89d66ec7333b8bca7fcc7dbb959fab689965637fd4
SocketDev~socket-patch~TM9M1F.dockerbuild
33.8 KB
sha256:a1574338d2481437882bd6ceb6de87157efd992ad77bbda35b72e5fe8956db42
SocketDev~socket-patch~TN9PVC.dockerbuild
15.9 KB
sha256:bc106766d194a02157bfc52d7e70001ff08e99b898e79ae084cb2a5d555c8c92
SocketDev~socket-patch~UU3SID.dockerbuild
24.4 KB
sha256:53a0e9ecbb828dce59b2fbc8f16c084fd2a9b46bf2f7538c7ab9b9429ca40bb5
SocketDev~socket-patch~VRRRX6.dockerbuild
32.8 KB
sha256:30f097b57f3c87493627a2b3d87835cba84a630336764d9c54d0a75f4eb72244
SocketDev~socket-patch~WULZBR.dockerbuild
21.9 KB
sha256:3b465d30decbd3e06a223395fa097e116a3f83b413156f4201245b0e91b15d96
SocketDev~socket-patch~WXPBF7.dockerbuild
18 KB
sha256:8f2540a53669d08b5785776ecdb9036d6dfc9517f6d158d6063dab5a8d7b116b
SocketDev~socket-patch~X6XEV0.dockerbuild
33.5 KB
sha256:2c0841b77bdbeeb2b0d2427da61b3a83e6b165dc38f1cd91a8f08abd441a528e
SocketDev~socket-patch~XSCLM0.dockerbuild
20.8 KB
sha256:e7b990160ff0b585deb712dddafaab3c45ccdcb755af5597a2d8c8fae61a0f22
SocketDev~socket-patch~YMKC06.dockerbuild
34.2 KB
sha256:d1d1dec680bb365aefd6056c1c2acb4cdbcb3b8f9943e98c12e346cf38445f7b
coverage-docker-cargo
35.9 KB
sha256:e41322d6492aebdea4cf95d0a3f84738173c30a07d4086ac4016048106040d73
coverage-docker-composer
36 KB
sha256:c46ebc2169531a054fe5ac64e070ccd80c651d267b7d678aa2978b15c0b93ba5
coverage-docker-deno
35.9 KB
sha256:cfb77b2249c8413d3dbf93651a116685b51ac64366b91f3f2fa53dc43bb5307e
coverage-docker-golang
35.9 KB
sha256:7bb1e0b02c3993c446692de94e5b85144c4ff5aea35e3e47ba4fe38da882f324
coverage-docker-maven
35.9 KB
sha256:4141d687d4f5d7fa3fc75dcd15850fb9a5f8f567ec6d134fc8f1133cbdfa2cd7
coverage-docker-npm
35.9 KB
sha256:8aaca953c85e2440c461b482cdfa1c6788613b4035043101515f8010c2bef0e9
coverage-docker-nuget
35.9 KB
sha256:eb985750f98780148fbfc176f57a05f115997a8abb355926ce19cae601daac77
coverage-docker-pypi
35.9 KB
sha256:dbca8ff03aff7f480e3d055bbb6b384e0afd31801bc6d129298efde43e2c73af
coverage-host
126 KB
sha256:8efc595338a59f917f368857ef69c1f1341016909f6ad6b19434ccd31b3ba7e0
setup-matrix-cargo
926 Bytes
sha256:53ababdb30a5209e409240bb83d50ee446cc1d8983f78dedbb12c8ffb5af61e8
setup-matrix-composer
917 Bytes
sha256:4b7d26641b1f5cb0c57ac67f1d28ebf88b42c3c19310547a7da7c6f715998f6c
setup-matrix-deno
902 Bytes
sha256:a293e8243f1ce3839bdca1d1f63597f9f2239a506359594af540e7ae6ff266d2
setup-matrix-gem
918 Bytes
sha256:751a00e31dd998f160bf81d010190f5fdd6c2fff961a89685b9c64fd3a42a485
setup-matrix-golang
905 Bytes
sha256:09ca825d380e16695f83a2dae6b539b5635bcc0b97ba11d8a5a643bfac1ee93a
setup-matrix-maven
914 Bytes
sha256:27aa26255d27f7f53ffe27bcc6b73b2d52514a163a3fa597941ab471203a11ec
setup-matrix-npm
1.73 KB
sha256:bbbb6ce176697e41acadb74fdd346479e0db7c853a18de4a6cfdd58842885ada
setup-matrix-nuget
910 Bytes
sha256:696b7024f172d1d7f8e11f02c366c167e963a316894755286dea039a1ca7101e
setup-matrix-pypi
1.82 KB
sha256:37b29ef63aeaac1c66d59f6fab277bd4d8c6498c2debce3fd08955d1b49adf3e