Open
Description
Before You File a Documentation Request Please Confirm You Have Done The Following...
- I have looked for existing open or closed documentation requests that match my proposal.
- I have read the FAQ and my problem is not listed.
Suggested Changes
Discussion from #9399 -> #9400 -> #9420 brought up a good edge case in our docs. Right now, we have two separate processes:
- New major version releases: https://typescript-eslint.io/maintenance/releases
- New versions of dependencies: https://typescript-eslint.io/maintenance/pull-requests/dependency-version-upgrades
...but what happens if both happen at the same time? I.e. if we're working on a new major version in a v* branch, and support for a new TypeScript major lands only only main? Users of the v* branch will have to wait until the next time we coincidentally merge changes from main into the v* branch.
Not ideal. We should update our docs, I think, to make it explicit that merging the latest main into v* should happen ASAP upon new major dependency support landing.
Affected URL(s)
Either or both of:
Metadata
Metadata
Assignees
Labels
Documentation ("docs") that needs adding/updatingDocumentation ("docs") that needs adding/updatingA member of the typescript-eslint team should work on this.A member of the typescript-eslint team should work on this.