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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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 (8.55.0 → 8.56.0) · Repo · Changelog
Release Notes
8.56.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
8.56.0Build: changelog update for 8.56.0chore: upgrade @eslint/js@8.56.0 (#17864)chore: package.json update for @eslint/js releasefeat: Support custom severity when reporting unused disable directives (#17212)feat: fix no-restricted-properties false negatives with unknown objects (#17818)chore: update dependency markdownlint to ^0.32.0 (#17783)fix: `TypeError: fs.exists is not a function` on read-only file system (#17846)chore: add GitHub issue template for docs issues (#17845)chore: Convert rule tests to FlatRuleTester (#17819)docs: update link in ways-to-extend.md (#17839)chore: upgrade eslint-plugin-unicorn to v49.0.0 (#17837)chore: upgrade eslint-plugin-eslint-plugin v5.2.1 (#17838)chore: update eslint-plugin-n v16.4.0 (#17836)docs: Update READMEdocs: fix migration-guide example (#17829)docs: check config comments in rule examples (#17815)docs: remove mention about ESLint stylistic rules in readme (#17810)ci: unpin Node.js 21.2.0 (#17821)docs: Update READMEfix: suggestion with invalid syntax in no-promise-executor-return rule (#17812)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