-
Notifications
You must be signed in to change notification settings - Fork 40
test: add ESLint 8.x tests #200
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
Conversation
Anyone know what the status of this is? |
7365907
to
0aa330d
Compare
Codecov Report
@@ Coverage Diff @@
## main #200 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 15 15
Lines 563 560 -3
Branches 158 156 -2
=========================================
- Hits 563 560 -3
Continue to review full report at Codecov.
|
0aa330d
to
69fb046
Compare
101be4c
to
fb64e98
Compare
@weyert ESLint v8 is already supported, we're just not testing against it. @MichaelDeBoey we shouldn't need to do a breaking release for this (though we might need to for supporting (Feel free to do PRs for the other changes, like updating TypeScript, as they're still valuable) |
fb64e98
to
18316b0
Compare
c9bbcad
to
f0abb56
Compare
@MichaelDeBoey I think for now we should probably stick with just adding v8 to the matrix of eslint versions we test against - I don't think there's a need to change our version constraints for now (since you're technically tightening them) |
ee3defa
to
b1e95a2
Compare
8f10391
to
662e5c7
Compare
662e5c7
to
e2755c6
Compare
c2196c7
to
1aa9a85
Compare
@G-Rath Now that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be feat
since we're actually already compatible with ESLint v8, and that could give people looking at the changelogs the wrong impression.
Instead either ci
or chore
would be more appropriate.
}, | ||
"peerDependencies": { | ||
"eslint": ">=6.8" | ||
"eslint": "^6.8.0 || ^7.0.0 || ^8.0.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should leave the range as-is, since we might already be compatible with new eslint versions (e.g. we're already compatible with 8 as a plugin).
We can always constraint it in a bugfix release if we find we're not compatible in the future.
"eslint": "^6.8.0 || ^7.0.0 || ^8.0.0" | |
"eslint": ">=6.8" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes it more explicit that we're 100% supporting a certain version.
If ESLint v9 gets released, it will only be a small change here together with adding the tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Meanwhile developers would be stuck using ESLint v8 or lower until we were able to make that change, and we've already seen how hard it can be to add tests for a new ESLint version...
1aa9a85
to
7839b8a
Compare
🎉 This PR is included in version 4.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
ESLint v8.0.0 is released 🎉
Closes #190
Closes #252
Closes #253