Update typescript-eslint 8.56.1 → 8.57.0 (minor) - #2
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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 (8.56.1 → 8.57.0)
Sorry, we couldn't find anything useful about this release.
Commits
See the full diff on Github. The new version differs by 21 commits:
chore(release): publish 8.57.0chore(website): enable `fixedOverflowWidgets` in editor settings (#12115)docs(eslint-plugin): document no-unnecessary-condition limitation with object types (#12111)chore: use pnpm catalog (#12047)chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.7.0 (#12113)fix(eslint-plugin): [no-base-to-string] fix false positive for toString with overloads (#12089)test: correct snapshotfix(eslint-plugin): [prefer-promise-reject-errors] add allow `TypeOrValueSpecifier` to prefer-promise-reject-errors (#12094)fix(typescript-estree): if the template literal is tagged and the text has an invalid escape, `cooked` will be `null` (#11355)chore: shard eslint-plugin tests (#12082)docs: minor grammar adjustment (#12112)fix(eslint-plugin): guard against negative paramIndex in no-useless-default-assignment (#12077)fix(eslint-plugin): handle statically analyzable computed keys in prefer-readonly (#12079)chore(deps): update dependency typedoc-plugin-markdown to v4.10.0 (#12060)chore(deps): update dependency eslint-plugin-perfectionist to v5.6.0 (#12054)fix(eslint-plugin): [strict-void-return] false positives with overloads (#12055)fix(typescript-estree): switch back to use `ts.getModifiers()` (#12034)chore(deps): update dependency @microsoft/api-extractor to v7.57.6 (#12087)docs: use `defineConfig` in "How to use" (#12108)feat(eslint-plugin): [no-unnecessary-condition] allow literal loop conditions in for/do loops (#12080)chore: update vitest to 4.x (#12071)Commits
See the full diff on Github. The new version differs by 21 commits:
chore(release): publish 8.57.0chore(website): enable `fixedOverflowWidgets` in editor settings (#12115)docs(eslint-plugin): document no-unnecessary-condition limitation with object types (#12111)chore: use pnpm catalog (#12047)chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.7.0 (#12113)fix(eslint-plugin): [no-base-to-string] fix false positive for toString with overloads (#12089)test: correct snapshotfix(eslint-plugin): [prefer-promise-reject-errors] add allow `TypeOrValueSpecifier` to prefer-promise-reject-errors (#12094)fix(typescript-estree): if the template literal is tagged and the text has an invalid escape, `cooked` will be `null` (#11355)chore: shard eslint-plugin tests (#12082)docs: minor grammar adjustment (#12112)fix(eslint-plugin): guard against negative paramIndex in no-useless-default-assignment (#12077)fix(eslint-plugin): handle statically analyzable computed keys in prefer-readonly (#12079)chore(deps): update dependency typedoc-plugin-markdown to v4.10.0 (#12060)chore(deps): update dependency eslint-plugin-perfectionist to v5.6.0 (#12054)fix(eslint-plugin): [strict-void-return] false positives with overloads (#12055)fix(typescript-estree): switch back to use `ts.getModifiers()` (#12034)chore(deps): update dependency @microsoft/api-extractor to v7.57.6 (#12087)docs: use `defineConfig` in "How to use" (#12108)feat(eslint-plugin): [no-unnecessary-condition] allow literal loop conditions in for/do loops (#12080)chore: update vitest to 4.x (#12071)Commits
See the full diff on Github. The new version differs by 21 commits:
chore(release): publish 8.57.0chore(website): enable `fixedOverflowWidgets` in editor settings (#12115)docs(eslint-plugin): document no-unnecessary-condition limitation with object types (#12111)chore: use pnpm catalog (#12047)chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.7.0 (#12113)fix(eslint-plugin): [no-base-to-string] fix false positive for toString with overloads (#12089)test: correct snapshotfix(eslint-plugin): [prefer-promise-reject-errors] add allow `TypeOrValueSpecifier` to prefer-promise-reject-errors (#12094)fix(typescript-estree): if the template literal is tagged and the text has an invalid escape, `cooked` will be `null` (#11355)chore: shard eslint-plugin tests (#12082)docs: minor grammar adjustment (#12112)fix(eslint-plugin): guard against negative paramIndex in no-useless-default-assignment (#12077)fix(eslint-plugin): handle statically analyzable computed keys in prefer-readonly (#12079)chore(deps): update dependency typedoc-plugin-markdown to v4.10.0 (#12060)chore(deps): update dependency eslint-plugin-perfectionist to v5.6.0 (#12054)fix(eslint-plugin): [strict-void-return] false positives with overloads (#12055)fix(typescript-estree): switch back to use `ts.getModifiers()` (#12034)chore(deps): update dependency @microsoft/api-extractor to v7.57.6 (#12087)docs: use `defineConfig` in "How to use" (#12108)feat(eslint-plugin): [no-unnecessary-condition] allow literal loop conditions in for/do loops (#12080)chore: update vitest to 4.x (#12071)Release Notes
8.57.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
chore(release): publish 8.57.0chore(website): enable `fixedOverflowWidgets` in editor settings (#12115)docs(eslint-plugin): document no-unnecessary-condition limitation with object types (#12111)chore: use pnpm catalog (#12047)chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.7.0 (#12113)fix(eslint-plugin): [no-base-to-string] fix false positive for toString with overloads (#12089)test: correct snapshotfix(eslint-plugin): [prefer-promise-reject-errors] add allow `TypeOrValueSpecifier` to prefer-promise-reject-errors (#12094)fix(typescript-estree): if the template literal is tagged and the text has an invalid escape, `cooked` will be `null` (#11355)chore: shard eslint-plugin tests (#12082)docs: minor grammar adjustment (#12112)fix(eslint-plugin): guard against negative paramIndex in no-useless-default-assignment (#12077)fix(eslint-plugin): handle statically analyzable computed keys in prefer-readonly (#12079)chore(deps): update dependency typedoc-plugin-markdown to v4.10.0 (#12060)chore(deps): update dependency eslint-plugin-perfectionist to v5.6.0 (#12054)fix(eslint-plugin): [strict-void-return] false positives with overloads (#12055)fix(typescript-estree): switch back to use `ts.getModifiers()` (#12034)chore(deps): update dependency @microsoft/api-extractor to v7.57.6 (#12087)docs: use `defineConfig` in "How to use" (#12108)feat(eslint-plugin): [no-unnecessary-condition] allow literal loop conditions in for/do loops (#12080)chore: update vitest to 4.x (#12071)Commits
See the full diff on Github. The new version differs by 21 commits:
chore(release): publish 8.57.0chore(website): enable `fixedOverflowWidgets` in editor settings (#12115)docs(eslint-plugin): document no-unnecessary-condition limitation with object types (#12111)chore: use pnpm catalog (#12047)chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.7.0 (#12113)fix(eslint-plugin): [no-base-to-string] fix false positive for toString with overloads (#12089)test: correct snapshotfix(eslint-plugin): [prefer-promise-reject-errors] add allow `TypeOrValueSpecifier` to prefer-promise-reject-errors (#12094)fix(typescript-estree): if the template literal is tagged and the text has an invalid escape, `cooked` will be `null` (#11355)chore: shard eslint-plugin tests (#12082)docs: minor grammar adjustment (#12112)fix(eslint-plugin): guard against negative paramIndex in no-useless-default-assignment (#12077)fix(eslint-plugin): handle statically analyzable computed keys in prefer-readonly (#12079)chore(deps): update dependency typedoc-plugin-markdown to v4.10.0 (#12060)chore(deps): update dependency eslint-plugin-perfectionist to v5.6.0 (#12054)fix(eslint-plugin): [strict-void-return] false positives with overloads (#12055)fix(typescript-estree): switch back to use `ts.getModifiers()` (#12034)chore(deps): update dependency @microsoft/api-extractor to v7.57.6 (#12087)docs: use `defineConfig` in "How to use" (#12108)feat(eslint-plugin): [no-unnecessary-condition] allow literal loop conditions in for/do loops (#12080)chore: update vitest to 4.x (#12071)Release Notes
8.57.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
chore(release): publish 8.57.0chore(website): enable `fixedOverflowWidgets` in editor settings (#12115)docs(eslint-plugin): document no-unnecessary-condition limitation with object types (#12111)chore: use pnpm catalog (#12047)chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.7.0 (#12113)fix(eslint-plugin): [no-base-to-string] fix false positive for toString with overloads (#12089)test: correct snapshotfix(eslint-plugin): [prefer-promise-reject-errors] add allow `TypeOrValueSpecifier` to prefer-promise-reject-errors (#12094)fix(typescript-estree): if the template literal is tagged and the text has an invalid escape, `cooked` will be `null` (#11355)chore: shard eslint-plugin tests (#12082)docs: minor grammar adjustment (#12112)fix(eslint-plugin): guard against negative paramIndex in no-useless-default-assignment (#12077)fix(eslint-plugin): handle statically analyzable computed keys in prefer-readonly (#12079)chore(deps): update dependency typedoc-plugin-markdown to v4.10.0 (#12060)chore(deps): update dependency eslint-plugin-perfectionist to v5.6.0 (#12054)fix(eslint-plugin): [strict-void-return] false positives with overloads (#12055)fix(typescript-estree): switch back to use `ts.getModifiers()` (#12034)chore(deps): update dependency @microsoft/api-extractor to v7.57.6 (#12087)docs: use `defineConfig` in "How to use" (#12108)feat(eslint-plugin): [no-unnecessary-condition] allow literal loop conditions in for/do loops (#12080)chore: update vitest to 4.x (#12071)Release Notes
8.57.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
chore(release): publish 8.57.0chore(website): enable `fixedOverflowWidgets` in editor settings (#12115)docs(eslint-plugin): document no-unnecessary-condition limitation with object types (#12111)chore: use pnpm catalog (#12047)chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.7.0 (#12113)fix(eslint-plugin): [no-base-to-string] fix false positive for toString with overloads (#12089)test: correct snapshotfix(eslint-plugin): [prefer-promise-reject-errors] add allow `TypeOrValueSpecifier` to prefer-promise-reject-errors (#12094)fix(typescript-estree): if the template literal is tagged and the text has an invalid escape, `cooked` will be `null` (#11355)chore: shard eslint-plugin tests (#12082)docs: minor grammar adjustment (#12112)fix(eslint-plugin): guard against negative paramIndex in no-useless-default-assignment (#12077)fix(eslint-plugin): handle statically analyzable computed keys in prefer-readonly (#12079)chore(deps): update dependency typedoc-plugin-markdown to v4.10.0 (#12060)chore(deps): update dependency eslint-plugin-perfectionist to v5.6.0 (#12054)fix(eslint-plugin): [strict-void-return] false positives with overloads (#12055)fix(typescript-estree): switch back to use `ts.getModifiers()` (#12034)chore(deps): update dependency @microsoft/api-extractor to v7.57.6 (#12087)docs: use `defineConfig` in "How to use" (#12108)feat(eslint-plugin): [no-unnecessary-condition] allow literal loop conditions in for/do loops (#12080)chore: update vitest to 4.x (#12071)👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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