Skip to content

ci: remove changelog rollover from release workflow (#97) #259

ci: remove changelog rollover from release workflow (#97)

ci: remove changelog rollover from release workflow (#97) #259

Triggered via push June 2, 2026 19:01
Status Success
Total duration 15m 13s
Artifacts 74

ci.yml

on: push
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: setup-matrix
Matrix: e2e
coverage-merge
22s
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 (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 (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 (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 (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 (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 (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 (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/
setup-matrix (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (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 (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 (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-docker (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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 (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/
coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
coverage-merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (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/
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 (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_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_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_maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e (ubuntu-latest, e2e_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_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/
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~0BUWXV.dockerbuild
33.7 KB
sha256:d55b46dd00a2c1385eeed44c1e5d7a37f6374ae6bcf163ec65dde6f89dd6eaa9
SocketDev~socket-patch~0OVLRI.dockerbuild
18.8 KB
sha256:813dd84662bfe456b538a7adae1fbc3716f9481fba73b0927cd423e7284f8047
SocketDev~socket-patch~14P65R.dockerbuild
34.1 KB
sha256:18aafb875c2e773d170f48f2eaa25382b6aaee5ac905b757f5a0960ae55779df
SocketDev~socket-patch~1V4YHX.dockerbuild
33.4 KB
sha256:fa21ca892a5fa88722b6b89fcafe09edc1e09cddcd736e34d6bab7b6985ceb2a
SocketDev~socket-patch~2XCNE3.dockerbuild
33.3 KB
sha256:546dd9d76ec734c4b170dd015ecfe522cc8d89f6ede710b53022770ac3a12a48
SocketDev~socket-patch~447UVJ.dockerbuild
33.8 KB
sha256:b84fa6a3ac1ea8b26156a2a3bd21567353c98bf684d8adb6e5b41befd09a3045
SocketDev~socket-patch~48XL6Y.dockerbuild
18.6 KB
sha256:46d6e0081e990f69284521b831303258983c72a9608456cda70a723002258004
SocketDev~socket-patch~5ODMJK.dockerbuild
32.9 KB
sha256:008bc3035c053e0ea511ec015406a3377335ecd7d05356f0274b93ed7af256b3
SocketDev~socket-patch~6DI1ID.dockerbuild
33.8 KB
sha256:95b86b9ab8d9a80902ae8f87308f312bde540a6c056f61fccd3935764a317f3e
SocketDev~socket-patch~6VL4ZB.dockerbuild
20.5 KB
sha256:69f0e7148d3930425355854fd5280911051e563713d1cabbe65786975b774703
SocketDev~socket-patch~7SEOOZ.dockerbuild
21.4 KB
sha256:23e0f4919dde7a98dd66950776c282cf223b5a2365d16c27334aa186ed125c22
SocketDev~socket-patch~8J3H98.dockerbuild
21 KB
sha256:e1521adec55b9b42486fa0dd784ac6aca0cd8ebb9168ebf2de9fedf3e71d7e37
SocketDev~socket-patch~9LRUYX.dockerbuild
33.4 KB
sha256:39af998d09755997e9cb62e4f3ccecbba975603c9ee72e350eb67c929acee003
SocketDev~socket-patch~9SXQ98.dockerbuild
17.9 KB
sha256:b0bf291a2c11b46e74c87f4c3ea242044c5c37e45954ca8d2d1fd9ac14a9501f
SocketDev~socket-patch~BXU0X6.dockerbuild
23.6 KB
sha256:55009a659d9265d9fbc8a43279f1afa9b8e5f3883d99e7fdbd79411681618c53
SocketDev~socket-patch~CORR6U.dockerbuild
34.2 KB
sha256:55fa6ff2558bd91a92f79a28e1d262436ebf22ccf79eda9afc024d40310320b7
SocketDev~socket-patch~EXUALQ.dockerbuild
23.5 KB
sha256:960cac6f8ce0f192ab7c9b0eed1763be620b9fafad7640a3147601734bfc58cc
SocketDev~socket-patch~FDHCJA.dockerbuild
33.2 KB
sha256:a4a95a4ca5a9bcdf48761532796bffe1e9f6cff8e3c9518ba1b73ac6cb36642d
SocketDev~socket-patch~GJK9DN.dockerbuild
20.5 KB
sha256:2f8d0385e74b09bab8aa119b3936b709bf2f316f1396b92244d0dba48c4aa573
SocketDev~socket-patch~GVC2CW.dockerbuild
33.7 KB
sha256:4f2bcc419fc40be6014fef97748c01532076ae6a182da0182e5606aa63359762
SocketDev~socket-patch~H9NF3B.dockerbuild
34.6 KB
sha256:37159e354c3106876329c45726ee3b5ef207401f7065d0e23c255a2762affdb0
SocketDev~socket-patch~HVXL8B.dockerbuild
15.8 KB
sha256:0142baa198bb1ccddea43986256d9ac39945b332c96f1d5bd41070cd387df5f8
SocketDev~socket-patch~HWT8YS.dockerbuild
21 KB
sha256:0ae938ea12dba421b35ef7e878c666f5362cd645ea0fb52e4a0882fcbdd75fdd
SocketDev~socket-patch~IIM24U.dockerbuild
33.4 KB
sha256:96f99be440728b481ed9d006011e450427bbac90c0ed62cb001acd672214767b
SocketDev~socket-patch~INAFPZ.dockerbuild
34.5 KB
sha256:e6ee1979640eabd0c7539a7d986c7e5daefeedfd8ef0b2182ba30b4f7d023187
SocketDev~socket-patch~IOVGPW.dockerbuild
21.6 KB
sha256:2ae9df861f65eac99183916078f9b838e41a4548a81411d17b45ffa52d144db2
SocketDev~socket-patch~IXZ3TA.dockerbuild
23.9 KB
sha256:892a5e16ed368dd444181a37ea947d3847fc5ce2e08112c76bc6aa285326591c
SocketDev~socket-patch~IY6BN8.dockerbuild
11.1 KB
sha256:1c7219a442cd063163c1e12515bdfc677416fff8c67ec34a24be24df5a65fc84
SocketDev~socket-patch~JCLQXZ.dockerbuild
24 KB
sha256:a85994ab7e7c96e7996b8564e9f34e6cb39ae80ee9f52585779fbd1ee5742636
SocketDev~socket-patch~LLGM9V.dockerbuild
33.2 KB
sha256:500bc6e64356d3775b26d154a13cdcd7978c6449744429119067405305ca1199
SocketDev~socket-patch~LW46G2.dockerbuild
24.3 KB
sha256:30491cf9030187dd1fd54edf700cb20bdfa6eff2fb6443582c9c0873df6b5a5d
SocketDev~socket-patch~M8S7QS.dockerbuild
21.5 KB
sha256:21f534addcace0a77b709c10cb4ed950e7589a64ceca1b4db2826a64dc1225ed
SocketDev~socket-patch~MQPMTW.dockerbuild
10.8 KB
sha256:d684c7942de69d60bdff009c28efcedba308fde0b1cb998f53494803e7944e41
SocketDev~socket-patch~N5BS91.dockerbuild
20.5 KB
sha256:d8ec380701a1d60599a15187fb9101ec29f1a1a45015bd3b8dc1e1dc2ad1805a
SocketDev~socket-patch~NIQLP4.dockerbuild
21.9 KB
sha256:b087051121cae9a4e38c92f4ee0398d6ee9270ca96946e07a5554328aeffe6e5
SocketDev~socket-patch~NT15ZI.dockerbuild
34.3 KB
sha256:fa8e94dd1f33cf398ec9aca4b92d88bdaa7181df5a370e5baae27a8d855a2266
SocketDev~socket-patch~NUMXAT.dockerbuild
33.7 KB
sha256:c701e600ff1261c845894a4efcf51a1049fd99f0c18c8da2662166d5886a07cb
SocketDev~socket-patch~OFSQM3.dockerbuild
33.4 KB
sha256:550832520f87c8e0f467b5a36b16bf38a914689927142e97768a8178503f1b22
SocketDev~socket-patch~P9599J.dockerbuild
35 KB
sha256:079676fc478cedeff711d33dd625e7cf2808cac0c53cf48b9948bd1a5b51cac9
SocketDev~socket-patch~RGMMQ6.dockerbuild
17 KB
sha256:6cb6cd1ff1c77734e509c2ec421e5a6dd8b56ab2405ef4e91bcfd4c1a55967ec
SocketDev~socket-patch~RONZUB.dockerbuild
10.9 KB
sha256:64f2ccca7d21ac96feea4161ac0088aec2fddd8fa3e3658fc66077d886b13330
SocketDev~socket-patch~SF9ICJ.dockerbuild
32.9 KB
sha256:75eb497104738fa46e43fb5d8f1b951f7890cb925a6c8e93818a271c39a6b018
SocketDev~socket-patch~SISWOS.dockerbuild
32.4 KB
sha256:b3c5fc6f02007bae06b94dc48498b6bcde373a4d31c270e99989a5949921b695
SocketDev~socket-patch~SRFVT9.dockerbuild
22.3 KB
sha256:cee467946ec09638cccac2ebc2d818542fc5a770ac81519da0ae805fe1a62e65
SocketDev~socket-patch~TLKZ2U.dockerbuild
21.5 KB
sha256:732d594d7f074114ec83be9610e5bd6a5cc798c4eb7e04a42b93d3cb3ec145cf
SocketDev~socket-patch~U6PS3D.dockerbuild
34.1 KB
sha256:7a66acc1c726dba0c1bf7a2df3311aa27c7c632b5b0d302baa8bff93ddec7919
SocketDev~socket-patch~U6Z2XK.dockerbuild
32.7 KB
sha256:dd16e8e4e31f3b9a7f325ad84ba786dff3c004b213d9a7d7ffa49fe6928f8dc7
SocketDev~socket-patch~V7QJZK.dockerbuild
34.9 KB
sha256:a08e3f0d7b1115d9930df63c56f0f4b8ba5b1077f859ca71b489b9aed0aaed62
SocketDev~socket-patch~VOHJDD.dockerbuild
18.4 KB
sha256:02b9197b4d8e5b8cbad46797d0a0552f105a439358cb77eb11a803b87a4d0373
SocketDev~socket-patch~WB66DY.dockerbuild
33 KB
sha256:2e561fc977549ee8a312a97f0b0c9c420b3649f095fee68ccc4141fa0b512c37
SocketDev~socket-patch~WHFIWM.dockerbuild
24.6 KB
sha256:0f2901f6a0bbaaf48cb41bb6e865411b3ab74f0dab5375ce44c7a33c5f152efd
SocketDev~socket-patch~XIRGWM.dockerbuild
20.6 KB
sha256:3594e38f3daa8597b2740af2dcfaf8aedfbe7f412c3211ae38f3940c5cec90a8
SocketDev~socket-patch~YRX4B8.dockerbuild
33.5 KB
sha256:6fdb4dd5fbc003523f16eb7e84bde65db249ddaf7026e80e8202a6c2c7c24ff4
SocketDev~socket-patch~Z6A86P.dockerbuild
34.9 KB
sha256:80036297998f4afaea2651eb528b951d4d1e7373aa87614a41e4c83b8e5399b1
coverage-docker-cargo
35.1 KB
sha256:ef989bcea574cb2bf456da8771b91ca83d4492243bf1cbdee5f7d408cd6a6cec
coverage-docker-composer
35.1 KB
sha256:3265fe06b387ec781c07a3bca82b17d71dfa904939fbc716a269fb74c9a29c38
coverage-docker-deno
35.1 KB
sha256:0a828f5564cfb31906e82fdd66fc91e5643a9969d7a035b8be9b67543d5b1772
coverage-docker-gem
35.1 KB
sha256:45bbc61d76afaf6b5652b6f7701f96de0be85c579842ae7bfc06e56109c42e5a
coverage-docker-golang
35.1 KB
sha256:c7385c0e806673f27e53287913bc6881425688149f3d36dc2369846f994c499d
coverage-docker-maven
35.1 KB
sha256:d9abe686725601f0d98fa4eb9adbfe12917093a26234eb6fac1f8240411b02a1
coverage-docker-npm
35.1 KB
sha256:0de359e97d9cb2784e2860c39497a13923806426adf34ab0ac2739ba8dc7cbb7
coverage-docker-nuget
35.1 KB
sha256:c641a180f86f1657c139af38666047130bc006a0abf9eb44a9abb6bdc4750fd3
coverage-docker-pypi
35.1 KB
sha256:0f22dd6ad0b0fce51cd3e456acb6df9a250a54d3522a09c15c0dcaa865c0baff
coverage-host
123 KB
sha256:eb62f068fbeca2c3024669de4d80ed95fb70335857318123b8f75ee818fd6a5a
coverage-lcov
128 KB
sha256:ebafa0ea65ffd9658f470b233c0e2f0d3a8d80238f08e5d69a6d5475592b779c
setup-matrix-cargo
887 Bytes
sha256:75306ccaa56225b3e6ddf995e72688689151d9e184fb883cbb242f3839215f58
setup-matrix-composer
881 Bytes
sha256:70cd127d39ea77d73e5665bed985dbcd0cc4c9d51e0e21094e0c39312f9f0304
setup-matrix-deno
862 Bytes
sha256:eb96284c57028c7131af19f70f1ab335f6d6e727416f5e61a03b157e15f8b5ed
setup-matrix-gem
878 Bytes
sha256:6c289181b460f59719ff3c34ad0068556173065b4fac96e665fc33d95d8bdbf2
setup-matrix-golang
866 Bytes
sha256:cfdf6b08d31b65294bcd0c502e48d81bdda2df5947abd5dc809d5d919854b183
setup-matrix-maven
875 Bytes
sha256:56d9dad3a6133f880c943ca6336e55c09c48117f0f866221245c633aab34d992
setup-matrix-npm
1.61 KB
sha256:070eeac2f0a81754b0b27ffddaedfdd0899bbda66a82524e79bba2dd02192950
setup-matrix-nuget
867 Bytes
sha256:92113f2a3ba88efc33e248c4c1f259cadd89fb118b1261f2924734cb805171e7
setup-matrix-pypi
1.76 KB
sha256:0f938fef5b33c2f73d523a5bdec2c66c51dffb4f3aa09f6871df315598acce61