Update all of typescript-eslint 6.7.4 → 6.8.0 (minor) #281
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}
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.7.4 → 6.8.0) · Repo · Changelog
Release Notes
6.8.0
6.7.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
chore: publish v6.8.0build: fix introduced post-merge build break with no-useless-empty-exportfeat(eslint-plugin): add new extended rule `prefer-destructuring` (#7117)fix(eslint-plugin): [consistent-type-imports] import assertion checks added (#7722)fix(eslint-plugin): [no-shadow] fix static class generics for class expressions (#7724)fix(eslint-plugin): [no-useless-empty-export] exempt .d.ts (#7718)fix(eslint-plugin): [no-unsafe-member-access] report on only the accessed property (#7717)docs(eslint-plugin): deduplicate examples for no-explicit-any (#7715)docs: fix "Alternatively" typo (#7740)chore: use named import for `util` (#7669)chore: remove Playwright end-to-end website tests (#7730)chore: add discord and stackoverflow as links to issue template (#7645)docs(eslint-plugin): [explicit-function-return-type] fix typo in option name (#7728)chore: publish v6.7.5docs(website): mention how rule options should be handled (#7713)fix(eslint-plugin): [prefer-string-starts-ends-with] only report slice/substring with correct range (#7712)docs: fix prefer-optional-chain example for the unsafe fixes option (#7711)✳️ @typescript-eslint/parser (6.7.4 → 6.8.0) · Repo · Changelog
Release Notes
6.8.0
6.7.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
chore: publish v6.8.0build: fix introduced post-merge build break with no-useless-empty-exportfeat(eslint-plugin): add new extended rule `prefer-destructuring` (#7117)fix(eslint-plugin): [consistent-type-imports] import assertion checks added (#7722)fix(eslint-plugin): [no-shadow] fix static class generics for class expressions (#7724)fix(eslint-plugin): [no-useless-empty-export] exempt .d.ts (#7718)fix(eslint-plugin): [no-unsafe-member-access] report on only the accessed property (#7717)docs(eslint-plugin): deduplicate examples for no-explicit-any (#7715)docs: fix "Alternatively" typo (#7740)chore: use named import for `util` (#7669)chore: remove Playwright end-to-end website tests (#7730)chore: add discord and stackoverflow as links to issue template (#7645)docs(eslint-plugin): [explicit-function-return-type] fix typo in option name (#7728)chore: publish v6.7.5docs(website): mention how rule options should be handled (#7713)fix(eslint-plugin): [prefer-string-starts-ends-with] only report slice/substring with correct range (#7712)docs: fix prefer-optional-chain example for the unsafe fixes option (#7711)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