chore(deps): Update dependency typescript to v7 #45
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!45
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/typescript-7.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
~6.0.3→~7.0.0Release Notes
microsoft/TypeScript (typescript)
v7.0.2Compare Source
Configuration
📅 Schedule: (in timezone Europe/Copenhagen)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.
9f5dff5883fdc333a7f4fdc333a7f4eafa528402Closing — skipping TypeScript 7 until there is a concrete reason to move.
Not merely "wait for upstream". TS 7 ships without the programmatic compiler API and is explicitly designed to run side-by-side with TS 6 (announcement). That is why typescript-eslint cannot support it (typescript-eslint#12518), and why lint here dies at import time rather than on any rule:
typescript-estreetranslates TypeScript source into an ESTree AST for ESLint by calling the compiler API. With no API to call it cannot load, so seven packages failed identically and zero files were linted — there was nothing in this repo to fix.Second, independent blocker: Expo does not run on TS 7, and Expo — not the catalog — owns
apps/mobile's TypeScript version.expo.install.excludelists onlyreactand@sentry/react-native, soexpo install --fixmanages TS there.The shape is also wrong for the eventual upgrade. Because TS 7 is a side-by-side install, adopting it means adding TS 7 for compilation while keeping TS 6 for API consumers — not rewriting
~6.0.3to~7.0.0in the catalog andapps/mobile, which is what this PR does. This diff would not be the right starting point even once upstream unblocks.A follow-up parks
typescriptmajors behinddependencyDashboardApproval, so this reappears only when someone deliberately asks for it.Correction for the record: I earlier stated this PR touched only
apps/mobile. It bumps the catalog as well — I was reading a diff fetched before Renovate rebased the branch.Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future
7.xreleases. But if you manually upgrade to7.xthen Renovate will re-enableminorandpatchupdates automatically.If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
Pull request closed