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.30.6) · Repo · Changelog
Release Notes
5.30.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 8 commits:
chore: publish v5.30.6
chore: Bump parse-url from 6.0.0 to 6.0.2 (#5312)
chore: Bump prism-react-renderer from 1.3.3 to 1.3.5 (#5306)
chore: Bump @babel/runtime from 7.18.3 to 7.18.6 (#5307)
chore: Bump @babel/code-frame from 7.16.7 to 7.18.6 (#5308)
chore: Bump @babel/types from 7.18.4 to 7.18.7 (#5302)
chore: Bump @microsoft/api-extractor from 7.27.0 to 7.28.3 (#5304)
chore: Bump clsx from 1.1.1 to 1.2.0 (#5298)
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