chore: Add i18n rules, perf script, insights & URL opener #34
ci.yml
on: push
frontend
1m 15s
rust
6m 1s
rust-security
42s
desktop-debug-build
41s
Annotations
21 errors and 4 warnings
|
desktop-debug-build:
src/pages/dashboard/index.tsx#L21
Cannot find module '../../lib/insight-canonical' or its corresponding type declarations.
|
|
desktop-debug-build:
src/pages/onboarding/index.tsx#L11
Cannot find module '../../lib/onboarding-estimates' or its corresponding type declarations.
|
|
desktop-debug-build:
src/pages/insights/index.tsx#L507
Parameter 'paragraph' implicitly has an 'any' type.
|
|
desktop-debug-build:
src/pages/insights/index.tsx#L348
Parameter 'index' implicitly has an 'any' type.
|
|
desktop-debug-build:
src/pages/insights/index.tsx#L348
Parameter 'item' implicitly has an 'any' type.
|
|
desktop-debug-build:
src/pages/insights/index.tsx#L312
Parameter 'item' implicitly has an 'any' type.
|
|
desktop-debug-build:
src/pages/insights/index.tsx#L21
Cannot find module '../../lib/insight-canonical' or its corresponding type declarations.
|
|
desktop-debug-build:
src/pages/dashboard/index.tsx#L682
Parameter 'paragraph' implicitly has an 'any' type.
|
|
desktop-debug-build:
src/pages/dashboard/index.tsx#L634
Parameter 'item' implicitly has an 'any' type.
|
|
desktop-debug-build:
src/pages/dashboard/index.tsx#L21
Cannot find module '../../lib/insight-canonical' or its corresponding type declarations.
|
|
frontend:
src/pages/dashboard/index.tsx#L638
Unsafe argument of type `any` assigned to a parameter of type `{ profileId?: string | null | undefined; url?: string | null | undefined; domain?: string | null | undefined; title?: string | null | undefined; }`
|
|
frontend:
src/pages/dashboard/index.tsx#L636
Unsafe member access .url on an `any` value
|
|
frontend:
src/pages/dashboard/index.tsx#L636
Unsafe member access .historyId on an `any` value
|
|
frontend:
src/pages/dashboard/index.tsx#L634
Unsafe member access .map on a type that cannot be resolved
|
|
frontend:
src/pages/dashboard/index.tsx#L634
Unsafe call of a type that could not be resolved
|
|
frontend:
src/pages/dashboard/index.tsx#L633
Unsafe member access .length on a type that cannot be resolved
|
|
frontend:
src/pages/dashboard/index.tsx#L176
Unsafe call of a type that could not be resolved
|
|
frontend:
src/pages/dashboard/index.tsx#L175
Unsafe assignment of an error typed value
|
|
frontend:
src/pages/dashboard/index.tsx#L173
Unsafe call of a type that could not be resolved
|
|
frontend:
src/pages/dashboard/index.tsx#L172
Unsafe assignment of an error typed value
|
|
rust
Process completed with exit code 101.
|
|
desktop-debug-build
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/
|
|
rust-security
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 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/
|
|
frontend
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/
|
|
rust
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/
|