Update eslint 9.30.1 → 9.32.0 (minor) #18656
Merged
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint (9.30.1 → 9.32.0) · Repo · Changelog
Release Notes
9.32.0
9.31.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 37 commits:
9.32.0
Build: changelog update for 9.32.0
fix: Upgrade @eslint/js (#19971)
chore: package.json update for @eslint/js release
fix: Refactor reporting into FileReport (#19877)
ci: unpin `jiti` to version `^2.5.1` (#19970)
fix: bump @eslint/plugin-kit to 0.3.4 to resolve vulnerability (#19965)
ci: pin `jiti` to version 2.4.2 (#19964)
test: switch to flat config mode in `SourceCode` tests (#19953)
test: switch to flat config mode in eslint-fuzzer (#19960)
fix: report only global references in no-implied-eval (#19932)
docs: Update README
refactor: use `CustomRuleDefinitionType` in `JSRuleDefinition` (#19949)
feat: support explicit resource management in core rules (#19828)
chore: switch performance tests to hyperfine (#19919)
feat: support typescript types in accessor rules (#19882)
test: switch to flat config mode in `ast-utils` tests (#19948)
fix: remove outdated types in `ParserOptions.ecmaFeatures` (#19944)
chore: exclude `further_reading_links.json` from Prettier formatting (#19943)
fix: update execScript message in no-implied-eval rule (#19937)
9.31.0
Build: changelog update for 9.31.0
chore: upgrade to `@eslint/[email protected]` (#19935)
chore: package.json update for @eslint/js release
chore: update eslint (#19933)
docs: Update README
fix: retry on EMFILE when writing autofix results (#19926)
feat: output full actual location in rule tester if different (#19904)
docs: fix mismatch between `globalIgnores()` code and text (#19914)
chore: bump mocha to v11 (#19917)
fix: Remove incorrect RuleContext types (#19910)
feat: support explicit resource management in `no-loop-func` (#19895)
feat: support explicit resource management in `no-undef-init` (#19894)
feat: support explicit resource management in `init-declarations` (#19893)
feat: support explicit resource management in `no-const-assign` (#19892)
docs: Update README
docs: Update working on issues info (#19902)
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