Update all of typescript-eslint 7.15.0 → 7.16.0 (minor) #130
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 (7.15.0 → 7.16.0) · Repo · Changelog
Release Notes
7.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore(release): publish 7.16.0fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `allowArray` option is enabled (#9492)fix(website): react key error on internal pages of website (#9506)fix(eslint-plugin): [no-floating-promises] add `suggestions` to tests from #9263 `checkThenables` (#9515)fix(utils): context.parserPath may be undefined (#9486)feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)feat(eslint-plugin): add support for nested namespaces to unsafe-member-access (#9478)docs: add snapshot-related info sections to the Pull Requests documentation (#9302)feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new rule (#8903)feat(ast-spec): add parent property to AccessorProperty node types (#9487)docs: tseslint.config takes a spread argument, not an array (#9483)feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eval (#9462)fix(deps): update dependency @eslint-community/regexpp to v4.11.0 (#9497)chore: update sponsors (#9495)docs: [class-methods-use-this] fix typo (#9494)feat(rule-tester): stricter rule test validations (#9086)chore(deps): update dependency mocha to v10.5.2 (#9470)chore: update nx to 19.4.0 (#9484)chore(deps): update dependency knip to v5.23.0 (#9480)✳️ @typescript-eslint/parser (7.15.0 → 7.16.0) · Repo · Changelog
Release Notes
7.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore(release): publish 7.16.0fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `allowArray` option is enabled (#9492)fix(website): react key error on internal pages of website (#9506)fix(eslint-plugin): [no-floating-promises] add `suggestions` to tests from #9263 `checkThenables` (#9515)fix(utils): context.parserPath may be undefined (#9486)feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)feat(eslint-plugin): add support for nested namespaces to unsafe-member-access (#9478)docs: add snapshot-related info sections to the Pull Requests documentation (#9302)feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new rule (#8903)feat(ast-spec): add parent property to AccessorProperty node types (#9487)docs: tseslint.config takes a spread argument, not an array (#9483)feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eval (#9462)fix(deps): update dependency @eslint-community/regexpp to v4.11.0 (#9497)chore: update sponsors (#9495)docs: [class-methods-use-this] fix typo (#9494)feat(rule-tester): stricter rule test validations (#9086)chore(deps): update dependency mocha to v10.5.2 (#9470)chore: update nx to 19.4.0 (#9484)chore(deps): update dependency knip to v5.23.0 (#9480)Release Notes
7.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore(release): publish 7.16.0fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `allowArray` option is enabled (#9492)fix(website): react key error on internal pages of website (#9506)fix(eslint-plugin): [no-floating-promises] add `suggestions` to tests from #9263 `checkThenables` (#9515)fix(utils): context.parserPath may be undefined (#9486)feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)feat(eslint-plugin): add support for nested namespaces to unsafe-member-access (#9478)docs: add snapshot-related info sections to the Pull Requests documentation (#9302)feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new rule (#8903)feat(ast-spec): add parent property to AccessorProperty node types (#9487)docs: tseslint.config takes a spread argument, not an array (#9483)feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eval (#9462)fix(deps): update dependency @eslint-community/regexpp to v4.11.0 (#9497)chore: update sponsors (#9495)docs: [class-methods-use-this] fix typo (#9494)feat(rule-tester): stricter rule test validations (#9086)chore(deps): update dependency mocha to v10.5.2 (#9470)chore: update nx to 19.4.0 (#9484)chore(deps): update dependency knip to v5.23.0 (#9480)Release Notes
7.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore(release): publish 7.16.0fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `allowArray` option is enabled (#9492)fix(website): react key error on internal pages of website (#9506)fix(eslint-plugin): [no-floating-promises] add `suggestions` to tests from #9263 `checkThenables` (#9515)fix(utils): context.parserPath may be undefined (#9486)feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)feat(eslint-plugin): add support for nested namespaces to unsafe-member-access (#9478)docs: add snapshot-related info sections to the Pull Requests documentation (#9302)feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new rule (#8903)feat(ast-spec): add parent property to AccessorProperty node types (#9487)docs: tseslint.config takes a spread argument, not an array (#9483)feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eval (#9462)fix(deps): update dependency @eslint-community/regexpp to v4.11.0 (#9497)chore: update sponsors (#9495)docs: [class-methods-use-this] fix typo (#9494)feat(rule-tester): stricter rule test validations (#9086)chore(deps): update dependency mocha to v10.5.2 (#9470)chore: update nx to 19.4.0 (#9484)chore(deps): update dependency knip to v5.23.0 (#9480)Release Notes
7.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore(release): publish 7.16.0fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `allowArray` option is enabled (#9492)fix(website): react key error on internal pages of website (#9506)fix(eslint-plugin): [no-floating-promises] add `suggestions` to tests from #9263 `checkThenables` (#9515)fix(utils): context.parserPath may be undefined (#9486)feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)feat(eslint-plugin): add support for nested namespaces to unsafe-member-access (#9478)docs: add snapshot-related info sections to the Pull Requests documentation (#9302)feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new rule (#8903)feat(ast-spec): add parent property to AccessorProperty node types (#9487)docs: tseslint.config takes a spread argument, not an array (#9483)feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eval (#9462)fix(deps): update dependency @eslint-community/regexpp to v4.11.0 (#9497)chore: update sponsors (#9495)docs: [class-methods-use-this] fix typo (#9494)feat(rule-tester): stricter rule test validations (#9086)chore(deps): update dependency mocha to v10.5.2 (#9470)chore: update nx to 19.4.0 (#9484)chore(deps): update dependency knip to v5.23.0 (#9480)Release Notes
7.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore(release): publish 7.16.0fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `allowArray` option is enabled (#9492)fix(website): react key error on internal pages of website (#9506)fix(eslint-plugin): [no-floating-promises] add `suggestions` to tests from #9263 `checkThenables` (#9515)fix(utils): context.parserPath may be undefined (#9486)feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)feat(eslint-plugin): add support for nested namespaces to unsafe-member-access (#9478)docs: add snapshot-related info sections to the Pull Requests documentation (#9302)feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new rule (#8903)feat(ast-spec): add parent property to AccessorProperty node types (#9487)docs: tseslint.config takes a spread argument, not an array (#9483)feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eval (#9462)fix(deps): update dependency @eslint-community/regexpp to v4.11.0 (#9497)chore: update sponsors (#9495)docs: [class-methods-use-this] fix typo (#9494)feat(rule-tester): stricter rule test validations (#9086)chore(deps): update dependency mocha to v10.5.2 (#9470)chore: update nx to 19.4.0 (#9484)chore(deps): update dependency knip to v5.23.0 (#9480)Release Notes
7.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
chore(release): publish 7.16.0fix(eslint-plugin): [restrict-template-expressions] don't report tuples if `allowArray` option is enabled (#9492)fix(website): react key error on internal pages of website (#9506)fix(eslint-plugin): [no-floating-promises] add `suggestions` to tests from #9263 `checkThenables` (#9515)fix(utils): context.parserPath may be undefined (#9486)feat(eslint-plugin): [no-floating-promises] add checkThenables option (#9263)feat(eslint-plugin): add support for nested namespaces to unsafe-member-access (#9478)docs: add snapshot-related info sections to the Pull Requests documentation (#9302)feat(eslint-plugin): [no-unnecessary-parameter-property-assignment] add new rule (#8903)feat(ast-spec): add parent property to AccessorProperty node types (#9487)docs: tseslint.config takes a spread argument, not an array (#9483)feat(eslint-plugin): [no-unnecessary-type-parameters] port from v8 to v7 (#9473)chore(eslint-plugin): re-using logic from builtinSymbolLike in no-implied-eval (#9462)fix(deps): update dependency @eslint-community/regexpp to v4.11.0 (#9497)chore: update sponsors (#9495)docs: [class-methods-use-this] fix typo (#9494)feat(rule-tester): stricter rule test validations (#9086)chore(deps): update dependency mocha to v10.5.2 (#9470)chore: update nx to 19.4.0 (#9484)chore(deps): update dependency knip to v5.23.0 (#9480)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