Update all of typescript-eslint 6.13.1 → 6.13.2 (patch) #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #56 +/- ##
=======================================
Coverage 91.62% 91.62%
=======================================
Files 10 10
Lines 203 203
Branches 21 21
=======================================
Hits 186 186
Misses 15 15
Partials 2 2 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @typescript-eslint/eslint-plugin (6.13.1 → 6.13.2) · Repo · Changelog
Release Notes
6.13.2
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 v6.13.2chore(website): use less text for type checked filter (#7993)docs: add 'When Not To Use It' or an intentional omission notice on all rules (#7447)chore: finish enabling no-unnecessary-condition internally (#8004)chore(deps): update babel to v7.23.4 (#7978)chore(deps): update babel to 7.23.3 (#7922)chore(website): fixed most no-unnecessary-condition complaints (#7836)chore: streamline issue templates (#7994)docs: updated globalSetup to setupFiles (#8000)chore: prefix all nx package scripts with npx (#7988)✳️ @typescript-eslint/parser (6.13.1 → 6.13.2) · Repo · Changelog
Release Notes
6.13.2
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 v6.13.2chore(website): use less text for type checked filter (#7993)docs: add 'When Not To Use It' or an intentional omission notice on all rules (#7447)chore: finish enabling no-unnecessary-condition internally (#8004)chore(deps): update babel to v7.23.4 (#7978)chore(deps): update babel to 7.23.3 (#7922)chore(website): fixed most no-unnecessary-condition complaints (#7836)chore: streamline issue templates (#7994)docs: updated globalSetup to setupFiles (#8000)chore: prefix all nx package scripts with npx (#7988)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