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?
✳️ @typescript-eslint/eslint-plugin (^4.31.0 → ^5.11.0) · Repo · Changelog
Release Notes
5.11.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 10 commits:
chore: publish v5.11.0fix(eslint-plugin): [no-magic-numbers] fix invalid schema merging (#4517)fix(eslint-plugin): [non-nullable-type-assertion-style] fix false positive when asserting to a generic type that might be nullish (#4509)docs: explicitly ask for PR template checklist being true and checked (#4511)chore: docusaurus@2.0.0-beta.15 (#4488)feat(eslint-plugin): [explicit-function-return-type] add allowedNames (#4440)chore: bump lint-staged from 12.3.1 to 12.3.2 (#4497)chore: bump eslint-plugin-jest from 25.7.0 to 26.0.0 (#4498)chore: bump rollup from 2.66.0 to 2.66.1 (#4499)chore: bump json-schema from 0.2.3 to 0.4.0 (#4496)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