Skip to content

⚡ optimize: replace synchronous I/O with asynchronous in app.ts #175

⚡ optimize: replace synchronous I/O with asynchronous in app.ts

⚡ optimize: replace synchronous I/O with asynchronous in app.ts #175

Triggered via pull request April 4, 2026 16:52
Status Failure
Total duration 11s
Artifacts

lint.yml

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

Annotations

10 errors and 1 warning
lint (20.x): src/versions.ts#L585
Type 'string | number' is not assignable to type 'string'.
lint (20.x): src/versions.ts#L578
Type 'string | number' is not assignable to type 'string'.
lint (20.x): src/versions.ts#L561
Argument of type 'string | number' is not assignable to parameter of type 'string'.
lint (20.x): src/versions.ts#L511
Argument of type 'string | number' is not assignable to parameter of type 'string'.
lint (20.x): src/versions.ts#L488
Argument of type 'string | number' is not assignable to parameter of type 'string'.
lint (20.x): src/versions.ts#L483
Argument of type 'number' is not assignable to parameter of type 'string'.
lint (20.x): src/provider.ts#L167
Property 'platform' is missing in type '{ appId: number; appKey: string; }' but required in type '{ appId: string; platform: Platform; }'.
lint (20.x): src/package.ts#L351
Conversion of type 'number' to type 'string' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
lint (20.x): src/package.ts#L333
Argument of type 'number' is not assignable to parameter of type 'string'.
lint (20.x): src/package.ts#L102
This comparison appears to be unintentional because the types 'string' and 'number' have no overlap.
lint (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@v4, actions/setup-node@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/