💥 (eslint) NICE-130 swap to ongoing canary|next [skip ci] #1513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BREAKING CHANGE: Move to 5.0.0-canary to track ongoing eslint7=>8
JeromeFitz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the risk of bumping a major every single time we upgrade package(s) from
eslint@8 => eslint@9we are going to use:main=>@jeromefitz/eslint-conifg@5.0.0-canaryNICE-XYZ=>@jeromefitz/eslint-conifg@5.0.0-nextThis way we can take our time as the eslint ecosystem takes theirs, and continue to use prereleases that can have more breaking changes without holding everything up. ➕
BREAKING CHANGE: Move to 5.0.0-canary to track ongoing eslint 9 migration