eslint-plugin: [no-invalid-void-type] allow using void as a default type for a generic argument if allowInGenericTypeArguments is specified (#5671) (bb46ef0)
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.39.0) · Repo · Changelog
Release Notes
5.39.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 7 commits:
chore: publish v5.39.0
chore: update sponsors (#5721)
docs: Audit and streamline CONTRIBUTING.md (#5595)
feat(eslint-plugin): allow using void as a default type for a generic argument if allowInGenericTypeArguments is specified (#5671)
chore: GitHub Workflows security hardening (#5672)
chore: update contributors (#5700)
chore(website): Enable react-hooks exhaustive deps rules (#5663)
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