fix: correctly detect type info in badge #8557
ci.yml
on: pull_request
π Lint project
27s
πͺ Type check
1m 10s
π§ͺ Unit tests
48s
π§ͺ Component tests
1m 54s
π₯οΈ Browser tests
3m 14s
π§Ή Unused code check
41s
π i18n validation
29s
Matrix: βΏ Accessibility audit
Annotations
14 errors and 3 warnings
|
π Lint project
Process completed with exit code 1.
|
|
πͺ Type check:
shared/utils/package-analysis.ts#L118
Cannot find name 'getLatestVersion'. Did you mean 'fetchLatestVersion'?
|
|
πͺ Type check:
shared/utils/package-analysis.ts#L118
Cannot find name 'getLatestVersion'. Did you mean 'fetchLatestVersion'?
|
|
πͺ Type check:
shared/utils/package-analysis.ts#L118
Cannot find name 'getLatestVersion'. Did you mean 'fetchLatestVersion'?
|
|
πͺ Type check:
server/api/registry/analysis/[...pkg].get.ts#L31
'AnalysisPackageJson' is declared but never used.
|
|
πͺ Type check:
server/api/registry/analysis/[...pkg].get.ts#L29
'getLatestVersion' is declared but its value is never read.
|
|
πͺ Type check:
server/api/registry/analysis/[...pkg].get.ts#L28
'getPackageFileTree' is declared but its value is never read.
|
|
πͺ Type check:
server/api/registry/analysis/[...pkg].get.ts#L27
'flattenFileTree' is declared but its value is never read.
|
|
πͺ Type check:
server/api/registry/analysis/[...pkg].get.ts#L13
'hasBuiltInTypes' is declared but its value is never read.
|
|
πͺ Type check:
server/api/registry/analysis/[...pkg].get.ts#L11
'getTypesPackageName' is declared but its value is never read.
|
|
πͺ Type check:
server/api/registry/analysis/[...pkg].get.ts#L6
'TypesPackageInfo' is declared but never used.
|
|
π₯οΈ Browser tests
Canceling since a higher priority waiting request for ci-2173 exists
|
|
π₯οΈ Browser tests
The operation was canceled.
|
|
ci
Canceling since a higher priority waiting request for ci-2173 exists
|
|
π§ͺ Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: codecov/test-results-action@0fa95f0e1eeaafde2c782583b36b28ad0d8c77d3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π§ͺ Unit tests
This action is being deprecated in favor of 'codecov-action'.
Please update CI accordingly to use 'codecov-action@v5' with
'report_type: test_results'.
The 'codecov-action' should and can be run at least once for
coverage and once for test results
|
|
π§ͺ Component tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|