-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(NA): upgrade typescript into v5.1.6 #186437
Conversation
@elastic/kibana-core I believe |
@mistic ack! I'll take a look today |
My first look shows that the new version of TS changed the module resolution APIs. We need to adapt this section of the code for that: kibana/packages/kbn-telemetry-tools/src/tools/utils.ts Lines 149 to 156 in e5fa891
Unit tests in that package already highlight that, so it should be "easier" to iterate. |
@elastic/ml-ui I think the schema extractor would have to also be updated to work properly on TS v5. I've skipped for now the jest tests that were failing here. I made some experiments but the unit tests keep getting different outputs from what you have there now and I didn't want to make more assumptions. Could you please take a look on it? |
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
# Backport This will backport the following commits from `main` to `8.15`: - [chore(NA): upgrade typescript into v5.1.6 (#186437)](#186437) --------- Co-authored-by: kibanamachine <[email protected]>
This PR bumps the Typescript version used on Kibana into v5.1.6. The full set of changes can be found here and here.
In order to make assumptions over the codebase and all the type of errors I choose to mark the failures with
@ts-expect-error
and let each team decide how to handle it.There is a list below with the files (and teams those belong to) where the annotations were added. If each team could provide help of fixing the ones under their domain it would be fantastic. It can be done in this PR or in subsequent ones.
Here it goes the list for follow up:
@elastic/kibana-core
@elastic/kibana-data-discovery
@elastic/obs-knowledge-team
@elastic/kibana-esql
@elastic/kibana-management
@elastic/kibana-security
@elastic/appex-sharedux
@elastic/kibana-visualizations
@elastic/kibana-presentation
@elastic/response-ops
@elastic/ml-ui
@elastic/search-kibana
@elastic/fleet
@elastic/kibana-gis
@elastic/stack-monitoring
@elastic/obs-ux-infra_services-team
@elastic/obs-ai-assistant
@elastic/search-kibana
@elastic/kibana-security
@elastic/security-solution
@elastic/security-threat-hunting-investigations
@elastic/obs-ux-management-team