.github/workflows/test.yml

deps(renovate): update dependency @types/node to v20.19.39 #3934

Sign in to view logs

Triggered via pull request April 6, 2026 14:01

synchronize #678

renovate/node-20.x

Status Failure

Total duration 2m 1s

Artifacts –

test.yml

on: pull_request

Matrix: Test

Annotations

33 errors and 10 warnings

Test (macos-latest, 16.x)

Process completed with exit code 2.

Test (macos-latest, 16.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (macos-latest, 16.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (ubuntu-latest, 16.x)

Process completed with exit code 2.

Test (ubuntu-latest, 16.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (ubuntu-latest, 16.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (ubuntu-latest, 20.x)

Process completed with exit code 2.

Test (ubuntu-latest, 20.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (ubuntu-latest, 20.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (ubuntu-latest, 18.x)

Process completed with exit code 2.

Test (ubuntu-latest, 18.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (ubuntu-latest, 18.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Process completed with exit code 1.

Lint: src/parseMessage.mts#L11

Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator

Lint: src/exec.mts#L22

Unsafe call of an `any` typed value

Lint: src/exec.mts#L22

Unsafe assignment of an `any` value

Lint: src/exec.mts#L21

Unsafe call of an `any` typed value

Lint: src/exec.mts#L21

Unsafe assignment of an `any` value

Test (macos-latest, 20.x)

Process completed with exit code 2.

Test (macos-latest, 20.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (macos-latest, 20.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (windows-latest, 16.x)

Process completed with exit code 1.

Test (windows-latest, 16.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (windows-latest, 16.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (windows-latest, 20.x)

Process completed with exit code 1.

Test (windows-latest, 20.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (windows-latest, 20.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (windows-latest, 18.x)

Process completed with exit code 1.

Test (windows-latest, 18.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (windows-latest, 18.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (macos-latest, 18.x)

Process completed with exit code 2.

Test (macos-latest, 18.x): src/exec.mts#L22

Property 'trim' does not exist on type 'string | Buffer'.

Test (macos-latest, 18.x): src/exec.mts#L21

Property 'trim' does not exist on type 'string | Buffer'.

Test (macos-latest, 16.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 16.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 20.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 18.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 20.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 16.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 20.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 18.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, 18.x)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/