Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Docs: Add mention of forward-porting dependency version support to in-progress major versions #9422

Copy link
Copy link
Open
@JoshuaKGoldberg

Description

@JoshuaKGoldberg
Issue body actions

Before You File a Documentation Request Please Confirm You Have Done The Following...

Suggested Changes

Discussion from #9399 -> #9400 -> #9420 brought up a good edge case in our docs. Right now, we have two separate processes:

...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

No one assigned

    Labels

    documentationDocumentation ("docs") that needs adding/updatingDocumentation ("docs") that needs adding/updatingteam assignedA member of the typescript-eslint team should work on this.A member of the typescript-eslint team should work on this.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.