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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint (^7.0.0 → ^8.4.0) · Repo · Changelog
Release Notes
8.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 26 commits:
8.4.0
Build: changelog update for 8.4.0
chore: upgrade @eslint/eslintrc@1.0.5 (#15389)
feat: add `allowReserved` parser option (#15387)
feat: Flat config support in Linter (refs #13481) (#15185)
docs: update integrations.md (#15380)
feat: Treat Class/New Expressions as truthy in no-constant-condition (#15326)
Sponsors: Sync README with website
feat: report only lines that exceed the limit in max-lines-per-function (#15140)
docs: fix typo in PR template (#15365)
chore: fix update-readme to avoid multiple consecutive blank lines (#15375)
feat: pass cwd to formatters (refs eslint/rfcs#57) (#13392)
Sponsors: Sync README with website
chore: Use default Chromium binary in M1 Mac tests (#15371)
fix: mark --rulesdir option as deprecated in CLI docs (#15310)
docs: enable a few more markdownlint rules and fix violations (#15368)
Sponsors: Sync README with website
ci: use node `v16` for Verify Files (#15364)
docs: Dedent needlessly indented example in getter-return docs (#15363)
Sponsors: Sync README with website
Sponsors: Sync README with website
docs: Update release notes blog post template (#15285)
feat: support async formatters (#15243)
chore: add jsdoc type annotation to rules (#15291)
Sponsors: Sync README with website
Sponsors: Sync README with website
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands