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 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)
depfu[bot]
commented
2 years ago
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.1.0) · Repo · Changelog
Release Notes
8.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 18 commits:
8.1.0Build: changelog update for 8.1.0Docs: Update commit message format docs (#15200)Fix: keyword-spacing conflict with space-infix-ops on `>` (fixes #14712) (#15172)Fix: allow `baseConfig` to extend preloaded plugin config (fixes #15079) (#15187)New: Add no-unused-private-class-members rule (fixes #14859) (#14895)New: Add name to RuleTester (#15179)Chore: improve performance of `:function` selector (#15181)Chore: fix counting of files in performance test (#15190)Build: add node v17 (#15193)Docs: remove `instanceof` from keyword-spacing docs (#15180)Upgrade: `eslint-plugin-eslint-plugin` to v4 (#15169)Docs: Describe range in rule docs (fixes #14162) (#15174)Chore: Update stale bot settings (#15173)Docs: Fix typo in README.md (#15168)Chore: migrate master to main (#15062)Chore: Add stale issue/PR checker (#15151)Docs: Update README team and sponsorsDepfu 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