chore(NA): upgrade typescript into v5.9.3#239670
Conversation
sabarasaba
left a comment
There was a problem hiding this comment.
Patched @elastic/kibana-management file with 8345e4c
|
@sabarasaba even before I've opened the PR 😄 Thank you for the fixes 😊 |
5485993 to
b0b2358
Compare
…ally, or add an exception to src/dev/yarn_deduplicate/index.ts and then commit the changes and push to your branch
davismcphee
left a comment
There was a problem hiding this comment.
Pushed some fixes for the Data Discovery types in 337659e, LGTM 👍
💚 Build Succeeded
Metrics [docs]Any counts in public APIs
Async chunks
History
|
|
We have a good amount of approvals and fixes in, the others could be done in further PRs. I'm going ahead and merge this in. |
|
Starting backport for target branches: 8.19, 9.1, 9.2 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
|
@mistic Huge achievement getting us from a 2-year-old version of Typescript to the latest! I don't think we've ever been on the cutting edge before. Amazing job! Ps. So hyped about finally having inferred type predicates (aka |
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
1 similar comment
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
|
@sorenlouv thank you! We wanted to get ready to try the new native TS compiler once it gets released 😎 |
Closes https://github.com/elastic/kibana-operations/issues/306
This PR bumps the Typescript version used on Kibana into v5.9.3. The full set of changes can be found here.
In order to make assumptions over the codebase and all the type of errors I choose to mark the failures with
@ts-expect-errorand 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/response-ops
@elastic/kibana-visualizations PR that will address these changes #241765
@elastic/kibana-data-discovery
@elastic/kibana-management
@elastic/kibana-presentation
@elastic/appex-sharedux
@elastic/obs-ai-assistant
@elastic/ml-ui
@elastic/kibana-cases
@elastic/obs-ux-logs-team
@elastic/fleet
@elastic/kibana-reporting-services
@elastic/kibana-security
@elastic/streams-program-team
@elastic/obs-ux-infra_services-team
@elastic/obs-ux-management-team
@elastic/security-detection-engine
@elastic/security-solution