-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Enhancement: Raise minimum versions of dependencies for v8 #8929
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
Comments
We should probably bump this to match ESLint again. They're using |
It's currently at |
What is the policy for Typescript version requirements? I think that bump is fine and I’m just curious if there is some guideline how you define it. :) |
@bradzacher thanks! I tried to search this info under maintenance and then didn’t use search 🤦 |
This comment has been minimized.
This comment has been minimized.
@iambumblehead unrelated. This is minimum versions. Not maximum versions. You want the pinned issue #8211 |
#8973 was merged into |
Overview
Our
v8
release is coming soon, and with that comes the regular expected bumping of our minimum dependency versions! 🎉To recap, raising the minimum versions of ESLint, Node, and TypeScript allows us to support fewer divergent sets of available APIs. That lets us work faster, ship less code, and take up fewer resources in our own builds. See https://typescript-eslint.io/users/dependency-versions for what version ranges we support.
This issue tracks raising the minimum versions of those three dependencies. Expecting roughly a ~summer 2024 release of v8:
Overall, this should be a pretty small change that doesn't cause much disruption. We can expect very few users to still require TypeScript 4.7.
Putting in
triage
so other folks on @typescript-eslint/triage-team can make sure I got this right. 😄💖
The text was updated successfully, but these errors were encountered: