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?
✳️ @typescript-eslint/eslint-plugin (^4.31.0 → ^5.13.0) · Repo · Changelog
Release Notes
5.13.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 12 commits:
chore: publish v5.13.0
Update README.md (#4592)
feat(eslint-plugin): [no-misused-promises] check more places for checksVoidReturn (#4541)
fix(eslint-plugin): [sort-type-union-intersection-members] Wrap the constructorType in parentheses (#4590)
feat(eslint-plugin): added member group support to member-ordering rule (#4538)
feat(eslint-plugin): add extension rule `space-before-blocks` (#1606) (#4184)
feat(utils): extract `isNotTokenOfTypeWithConditions` out of `ast-utils`' `predicates` (#4502)
feat(eslint-plugin): add `no-useless-empty-export` rule (#4380)
feat(eslint-plugin): add `no-redundant-type-constituents` rule (#4378)
feat(utils): expose `ast-utils`' helpers (#4503)
chore: bump webpack from 5.69.0 to 5.69.1 (#4579)
chore: bump rollup from 2.67.2 to 2.67.3 (#4578)
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