Skip to content

fix(tsconfig): make tsconfig files compatible with TypeScript 6.0 #2930

fix(tsconfig): make tsconfig files compatible with TypeScript 6.0

fix(tsconfig): make tsconfig files compatible with TypeScript 6.0 #2930

Triggered via pull request April 20, 2026 05:13
Status Failure
Total duration 50s
Artifacts

checks.yml

on: pull_request
Matrix: checks
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 4 warnings
ts:check
Parameter 'c' implicitly has an 'any' type.
ts:check
Cannot find namespace 'yargs'.
ts:check
'yargs' is declared but its value is never read.
ts:check
Parameter 'args' implicitly has an 'any' type.
ts:check
Parameter 'c' implicitly has an 'any' type.
ts:check
Cannot find namespace 'yargs'.
ts:check
'yargs' is declared but its value is never read.
ts:check
Unused '@ts-expect-error' directive.
ts:check
Parameter 'path' implicitly has an 'any' type.
ts:check
Parameter 'paths' implicitly has an 'any' type.
test
Parameter 'c' implicitly has an 'any' type.
test
Cannot find namespace 'yargs'.
test
'yargs' is declared but its value is never read.
test
Parameter 'args' implicitly has an 'any' type.
test
Parameter 'c' implicitly has an 'any' type.
test
Cannot find namespace 'yargs'.
test
'yargs' is declared but its value is never read.
test
Unused '@ts-expect-error' directive.
test
Parameter 'path' implicitly has an 'any' type.
test
Parameter 'paths' implicitly has an 'any' type.
lint:check
Parameter 'c' implicitly has an 'any' type.
lint:check
Cannot find namespace 'yargs'.
lint:check
'yargs' is declared but its value is never read.
lint:check
Parameter 'args' implicitly has an 'any' type.
lint:check
Parameter 'c' implicitly has an 'any' type.
lint:check
Cannot find namespace 'yargs'.
lint:check
'yargs' is declared but its value is never read.
lint:check
Unused '@ts-expect-error' directive.
lint:check
Parameter 'path' implicitly has an 'any' type.
lint:check
Parameter 'paths' implicitly has an 'any' type.
prettier:check
Parameter 'c' implicitly has an 'any' type.
prettier:check
Cannot find namespace 'yargs'.
prettier:check
'yargs' is declared but its value is never read.
prettier:check
Parameter 'args' implicitly has an 'any' type.
prettier:check
Parameter 'c' implicitly has an 'any' type.
prettier:check
Cannot find namespace 'yargs'.
prettier:check
'yargs' is declared but its value is never read.
prettier:check
Unused '@ts-expect-error' directive.
prettier:check
Parameter 'path' implicitly has an 'any' type.
prettier:check
Parameter 'paths' implicitly has an 'any' type.
ts:check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. 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/
lint:check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. 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/
prettier:check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. 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/