Update all of eslint 9.20.1 → 9.21.0 (minor) #2217
Open
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/js (9.20.0 → 9.21.0) · Repo · Changelog
Release Notes
9.21.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:
9.21.0
Build: changelog update for 9.21.0
chore: update `@eslint/eslintrc` and `@eslint/js` (#19453)
chore: package.json update for @eslint/js release
feat: introduce new deprecated types for rules (#19238)
test: add test for `Rule.ReportDescriptor` type (#19449)
chore: update rewrite dependencies (#19448)
docs: Update README
fix: update missing plugin message template (#19445)
fix: do not exit process on rule crash (#19436)
chore: better error message for missing plugin in config (#19402)
docs: replace `var` with `let` and `const` in rule example (#19434)
chore: set js language for bug report issue config block (#19439)
docs: Update README
docs: Update README
test: processors can return subpaths (#19425)
docs: Update Eleventy from v2 to v3 (#19415)
feat: Add `--ext` CLI option (#19405)
docs: Update README
9.20.1
Build: changelog update for 9.20.1
docs: allow typing in search box while dropdown is open (#19424)
fix: fix `RuleContext` type (#19417)
docs: Add instructions for pnpm compat (#19422)
docs: Fix Keyboard Navigation for Search Results (#19416)
docs: Update README
✳️ eslint (9.20.1 → 9.21.0) · Repo · Changelog
Release Notes
9.21.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
9.21.0
Build: changelog update for 9.21.0
chore: update `@eslint/eslintrc` and `@eslint/js` (#19453)
chore: package.json update for @eslint/js release
feat: introduce new deprecated types for rules (#19238)
test: add test for `Rule.ReportDescriptor` type (#19449)
chore: update rewrite dependencies (#19448)
docs: Update README
fix: update missing plugin message template (#19445)
fix: do not exit process on rule crash (#19436)
chore: better error message for missing plugin in config (#19402)
docs: replace `var` with `let` and `const` in rule example (#19434)
chore: set js language for bug report issue config block (#19439)
docs: Update README
docs: Update README
test: processors can return subpaths (#19425)
docs: Update Eleventy from v2 to v3 (#19415)
feat: Add `--ext` CLI option (#19405)
docs: Update README
Release Notes
3.3.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
chore: release 3.3.0 (#181)
feat: Add types to package (#179)
refactor: Upgrade ESLint (#178)
Release Notes
0.2.7 (from changelog)
0.2.6 (from changelog)
Does any of this look wrong? Please let us know.
Release Notes
3.3.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
3.3.1
Meta tweak
Fix Bun compatibility (#32)
Meta tweaks
🆕 @eslint/core (added, 0.12.0)
🗑️ @eslint/core (removed)
🗑️ @eslint/core (removed)
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