Skip to content

feat(setup): add --check and --remove flags with dry-run + edit previews #260

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

feat(setup): add --check and --remove flags with dry-run + edit previews #260

Triggered via pull request June 2, 2026 19:41
Status Success
Total duration 15m 5s
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 (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup-matrix (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-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 (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/
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 (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 (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 (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 (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 (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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/
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-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_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_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_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 (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~05NG27.dockerbuild
11.4 KB
sha256:ff4b5ec681774dbf914eba2241e3dd8f8cf2eff6b2fa37059acecb721011cecb
SocketDev~socket-patch~0MPMIB.dockerbuild
24.4 KB
sha256:0d00f69bb396e3c9f4b65ac6dd6ab9066cf241c46e7f74b5a2ac8a10371b33a5
SocketDev~socket-patch~4CAO1T.dockerbuild
33.5 KB
sha256:790973d412eedcb505779102e19bcd164386e61ed585ba56cca16829d2572a64
SocketDev~socket-patch~55IQ3K.dockerbuild
24 KB
sha256:4df18a16e32d6011e01a45a58bc2c67336fc9a819696944eb78dcde1de6cf43b
SocketDev~socket-patch~61X4QJ.dockerbuild
33.5 KB
sha256:d2114e9458a9dc3cdbe7a01a937bdebe1750d6240c8335a2abb74fc9cbcd88c6
SocketDev~socket-patch~7IKND3.dockerbuild
22.3 KB
sha256:8696e077fbd9c3f8ae8e4e7069fa5436df434800ffe40b12c9043b8796092c59
SocketDev~socket-patch~A15YPT.dockerbuild
34 KB
sha256:91c319b65b5c2620887f928e14afb963ae5a5eef689f056c6efd6b629612157b
SocketDev~socket-patch~AL9MNH.dockerbuild
33.1 KB
sha256:8cee37cc377525dffa55c18ed7d63aa3dc70434ff0bb76ca473136f7af7dca3b
SocketDev~socket-patch~AQQ5KW.dockerbuild
21.3 KB
sha256:1ee4074863c22d4c5009282767698bae5a43d6eb0385e6c68e6a30d3f66bd09d
SocketDev~socket-patch~AX64Y3.dockerbuild
32.8 KB
sha256:0817c440e9277ff5ef8315319c1ef5905173514e20e5a6dd2488a64bcb02e9e3
SocketDev~socket-patch~C5V4PV.dockerbuild
33.6 KB
sha256:9b0f95b8a42c8b19eb966c1443c2bc1849cae5b6f837a875a79df0ce80d3945e
SocketDev~socket-patch~D4802G.dockerbuild
18.1 KB
sha256:31980817840dee01f0e2ee1084eebbe61ac593ab877a4c3607066b443da86c89
SocketDev~socket-patch~FIJ2WZ.dockerbuild
20.6 KB
sha256:87b9f65b81176fa03fa43b4e164b5f0e8ae5866618230b9096b6c61273f84b38
SocketDev~socket-patch~FWO37I.dockerbuild
20.5 KB
sha256:dfe3596ec46e99561f5dc706a0f12f42a2aa609c1a246223b2619abd80f767f3
SocketDev~socket-patch~GHMMNH.dockerbuild
24.4 KB
sha256:17fb615636b2c8548d7e30036d571bcd865b50a34a33a17e61e65097ac492f5a
SocketDev~socket-patch~GPRDEI.dockerbuild
33.2 KB
sha256:b7d53dad33e1c2ae3f2bc8708b3b784d3a43f6401bb2be36771cd67c2cf0d61e
SocketDev~socket-patch~I2YSV6.dockerbuild
32.9 KB
sha256:5031c79d136a80334b1c7b9ef77f420d98a4f34870ca293423fbc61787301cde
SocketDev~socket-patch~IXEY9Z.dockerbuild
34 KB
sha256:f57842d1170ed5332e85fa3d5e3a1ba93af945fbdc145482cad2f82001caef95
SocketDev~socket-patch~JBNQV6.dockerbuild
33.1 KB
sha256:670f7deb3a420a68e4c6e5c23ea6ba3f82ae105d17fce8d3482cda1c869f8bc4
SocketDev~socket-patch~JE6GAX.dockerbuild
17.4 KB
sha256:e5edb1561d054d198a36ffad541ce32effca368eeddbebf564416f9043961df2
SocketDev~socket-patch~K5T8DK.dockerbuild
21.8 KB
sha256:bec5d28803a0449fd735b675647b470d9eb470d3eeb563a715f13dd9c25632d6
SocketDev~socket-patch~KFI4C3.dockerbuild
16.1 KB
sha256:9d18f46245ad506cb419a4533d0cce4d94cc00ad0483ad7d9c766866821897fa
SocketDev~socket-patch~KHADPB.dockerbuild
17.5 KB
sha256:42d84aac4e883b317640a06a99713502c444f99281474d60046e87fca299cd93
SocketDev~socket-patch~L0R8AJ.dockerbuild
20.2 KB
sha256:9aea717c022e48731d2b0a9acbd9bfe1440f3d2485e709aec911644e41e3725d
SocketDev~socket-patch~M56BU8.dockerbuild
33.3 KB
sha256:0f1e2f5b0ec2c5510b7d7cfe9948799ee26991d3434b8735b1f0290043141b80
SocketDev~socket-patch~M8LGP2.dockerbuild
33.6 KB
sha256:643142d8195d4451a6e19f174876e31e81cefae59b26c5713211290f277bf728
SocketDev~socket-patch~MMFS0C.dockerbuild
33.4 KB
sha256:394aa8adcd8d238a9219be7b2342c17f143f3a56e441fcca6d9d391309f82015
SocketDev~socket-patch~MMSL9T.dockerbuild
24.2 KB
sha256:38a393239262a6a28d935168e55327802f6b05fb0ba03ca2ba11250fb7a82b6c
SocketDev~socket-patch~MVF5PO.dockerbuild
23.8 KB
sha256:37c94aee1619dcaa1ad890d8ca2db05d0ea7a9cf1eb55d1f292dea30ecda3ae1
SocketDev~socket-patch~NZNNFF.dockerbuild
33 KB
sha256:e6701f322f48286086d79d12d41e76f490e67abbf533a8fc4d098491844ddc17
SocketDev~socket-patch~O257K8.dockerbuild
20.5 KB
sha256:e807715abb21132ae5e7c1fc5ac0a287864435dfd1801ef663db9f8cd6496470
SocketDev~socket-patch~OM3606.dockerbuild
33.6 KB
sha256:713e0e913a8b877aade93f93c717e58994fa37d7caa4b08e7a517a3b219db29d
SocketDev~socket-patch~OQG57R.dockerbuild
17 KB
sha256:ecaa2fdecadcdf596814a8dac82130331c92d2ebecffe4e720245fe50cbb69c8
SocketDev~socket-patch~PKW9HT.dockerbuild
33.4 KB
sha256:5f460a5bc9b56724d5a66e307ea76297ee0917e2709542a4b7e5627bb600ecf7
SocketDev~socket-patch~PLCYE1.dockerbuild
21.8 KB
sha256:a3a08bfd3043003f64b60cd2eba3af3527853f374c11567944e0a18f55c50e07
SocketDev~socket-patch~PSYX9J.dockerbuild
24.6 KB
sha256:a9760fe9d85a8c59a1f14ff62184e86539ca6e3f4caea4914a83b64ab28f3eae
SocketDev~socket-patch~QDGYF6.dockerbuild
33.9 KB
sha256:f0ec968f0032ab1ec75518aef7c4f13ae812befa3917d125c9e50525ca049c0e
SocketDev~socket-patch~QKQKEL.dockerbuild
18.5 KB
sha256:7da783dcc076bf4a2b0bc8dff7936aea9b766ca86f9fbd360b6d58797cae8f57
SocketDev~socket-patch~RZU7LG.dockerbuild
33.3 KB
sha256:f4b6e31d3ef9a66edb8f3182985b09b6e35a53a5c299ece80ad95804dabaae0c
SocketDev~socket-patch~S7ASQ4.dockerbuild
11.4 KB
sha256:c69aadf0ec85206351b5955423d931b45d2e56d277c71f3fff0ed9645dc54484
SocketDev~socket-patch~S82YIT.dockerbuild
21.5 KB
sha256:53c7407fa4c21328f989b076a29c1b1848134d92c7470a76ce3d1f305155df82
SocketDev~socket-patch~SI1446.dockerbuild
33.2 KB
sha256:9a20708e7aefce4a88e0eaceabdeb9ebae12c7db9de71e07443c70bb75ccb94c
SocketDev~socket-patch~SWIZC0.dockerbuild
33.3 KB
sha256:c3cc67807152a6bb3620c7aaf8010ef5658b51d4b8fe65e10090d0c6cbfebe88
SocketDev~socket-patch~TY5L9G.dockerbuild
33 KB
sha256:bcc921dc11adf25cf18cc40172ee6024a778f368e8c1361f949821a3e9abc33b
SocketDev~socket-patch~UWA2MO.dockerbuild
32.5 KB
sha256:66eabb4abb4769a8acc7ba411f965fae28010d521f9917485d34db3fa6f039c5
SocketDev~socket-patch~V7VYLC.dockerbuild
33.8 KB
sha256:b04bb411a108f9b5a65f1117a7bbe2c19a73ec9bb5f662c02fe076a9c9401ce2
SocketDev~socket-patch~VQ4WA9.dockerbuild
20 KB
sha256:4cfa2c9ee07ea016a6f079498b7634a4a3eeb1103f27810bb4929a550d092d00
SocketDev~socket-patch~WAVSVQ.dockerbuild
11 KB
sha256:672a0c54d392ce292988101d175ba93daecf5c4eb2999fc4794f8f003cc4c984
SocketDev~socket-patch~WJPCOI.dockerbuild
33.5 KB
sha256:38d7bcb2491c157b5c4df9d6ea5f85f4c6e8fba97ea7ccbe434f16c4c49cf54a
SocketDev~socket-patch~XCSGVN.dockerbuild
33.2 KB
sha256:82a5b413b7a95c7a28706021f7270f33862a23925216f8fcff5079bdb0932482
SocketDev~socket-patch~XKSFZG.dockerbuild
34.5 KB
sha256:e4482c7fb194c81e3ab4c3752aa088903a5a5dfd8a178bf90817987e5aaab154
SocketDev~socket-patch~XMZN4H.dockerbuild
21.8 KB
sha256:02fed40ce9f5d609b4a26108fe042fae226bd92bb37f2dbc0af03c1819613af5
SocketDev~socket-patch~YD60H7.dockerbuild
34.6 KB
sha256:f2a98949f6047a1f1215fe4fa4fc833128032a41946ad3ff7bc0d1f41ffcace5
SocketDev~socket-patch~YKZQHX.dockerbuild
21.8 KB
sha256:d9c653c1f9b83f1d0d801e004750bd3d9ab01b25789edbc084a3963d705e2a51
coverage-docker-cargo
35.9 KB
sha256:967ead1e807df8c7ca1d9dac744f284fc8e8cee3f489aaa5a93530d794d03a4c
coverage-docker-composer
36 KB
sha256:e0c07f1898987eda1be50aa8842646827673a1d640224c97e06f9854f120b92a
coverage-docker-deno
35.9 KB
sha256:e00d3da8a50155c2f4b6f656c5cdc1081645c1578ff659150260aed454e37ea0
coverage-docker-gem
35.9 KB
sha256:21ea96dfdd104c4025a8673041e775ccb6b0077d50ed442c940605f7862bfc8f
coverage-docker-golang
35.9 KB
sha256:744b33f0c8b7dee6b62bc06578d7a5a6e4f42b4acb1f7ecb13f4bbb8a309e3b8
coverage-docker-maven
35.9 KB
sha256:7e440dbcb5ad54d3b3144f89c907e5001205e328d96a75ac4522149a061c7639
coverage-docker-npm
35.9 KB
sha256:979de12d7c7a78f5a2a9b16a39afaf23fba0e957049f602ff8877ccc83d18214
coverage-docker-nuget
35.9 KB
sha256:3373bbe9aa90ce9ffc2eac25f4d8db332c46d72b256506ac8436e74d6ebf0ff7
coverage-docker-pypi
35.9 KB
sha256:415467db0312bc8412528c5aca51b65f34b6d0ed794cd9cd29afbe7a74a8af7f
coverage-host
126 KB
sha256:c2c43324aa50adbba96e5cceeaea370f89150f8abf5213de8b0f88b5c793c04e
coverage-lcov
131 KB
sha256:70cf21e53bd46b134f30d2254ba458f54ba44346cf66f49639a8fa6d6bbd9dd8
setup-matrix-cargo
930 Bytes
sha256:e8e28549224e60132df6c295fc70939e7a19989101f3c9444320e1e8eb8f2f8f
setup-matrix-composer
928 Bytes
sha256:05a2f09428681707f3773eefc689439710f7c934032ea7ebeb9b1a52a59e7d66
setup-matrix-deno
918 Bytes
sha256:0cceebc009b1f4d5b4a238179b770b3d5c6f23c6caa3dfa70c325692c79e5ae6
setup-matrix-gem
925 Bytes
sha256:72488ae948906f0dbd750e2147fb2f580a66fee6dc0ee2a629b328a23f7ea5ee
setup-matrix-golang
908 Bytes
sha256:08cd81c95b944455dd1b5d0e153d3e0b47902492169d2694c770ea6d783cbda1
setup-matrix-maven
915 Bytes
sha256:916a050024d9f142c94580c4b22d979d4a912d86523182d465d6355e9513fc80
setup-matrix-npm
1.73 KB
sha256:6f92b73ee0103cd707187790d0737a0f6f855c113be7e69b3975975dcd9cd84b
setup-matrix-nuget
915 Bytes
sha256:16839eeca33b98efbe4b608d7bf3364485dc70d0c35b49d6594cc2912d216734
setup-matrix-pypi
1.84 KB
sha256:39c0dfd727650ba050f9a6a6190dadac7abcb1d3c75292b5a0f24b53904bbe06