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)
Coverage remained the same at 82.941% when pulling 5c862d8b562337509c2e6cd8beb1a32a5af2a09f on depfu/update/npm/eslint-8.6.0 into 9dfe7efe675901582d2dacb6216069b0e9213198 on master.
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.6.0) · Repo · Changelog
Release Notes
8.6.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
8.6.0
Build: changelog update for 8.6.0
chore: Upgrade espree to 9.3.0 (#15473)
chore: Update blogpost.md.ejs (#15468)
docs: Document homedir is a configuration root (#15469)
feat: handle logical assignment in no-self-assign (#14152)
feat: allow to define `eslint-disable-next-line` in multiple lines (#15436)
docs: consistency changes (#15404)
refactor: remove unused parameter in `linter.js` (#15451)
test: add tests for `allowReserved` parser option with flat config (#15450)
Sponsors: Sync README with website
Sponsors: Sync README with website
feat: false negative with `onlyDeclarations` + `properties` in id-match (#15431)
docs: Mention character classes in no-useless-escape (#15421)
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