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)
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.32.0 → ^8.2.0) · Repo · Changelog
Release Notes
8.2.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
8.2.0
Build: changelog update for 8.2.0
chore: update @eslint/eslintrc to avoid different versions of `js-yaml` (#15265)
feat: report class evaluation TDZ errors in no-use-before-define (#15134)
perf: don't prepare a fix for valid code in key-spacing (#15239)
docs: Use string rule severity in CLI examples (#15253)
build: upgrade eslint-release to v3.2.0 to support conventional commits (#15246)
Sponsors: Sync README with website
Sponsors: Sync README with website
docs: fix typo in `working-with-rules.md` (#15233)
Sponsors: Sync README with website
docs: fix broken anchor in configuration files (#15223)
chore: update `strip-ansi` dependency (#15221)
docs: Link to unit tests from rule documentation (#15207)
docs: add `ci` and `perf` tags for commit (#15215)
ci: Remove Node 16 CI prerelease workaround (#14935)
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