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 cancel merge
Cancels automatic merging of this PR
@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)
coverage: 73.372%. remained the same when pulling 4470ba98b7ce4f1ac979d6afa1173bb3be913463 on depfu/update/npm/group/typescript-eslint-6.8.0 into b1e364b0e63297d65f3627b3d4b75f00f63bbb8f on master.
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.0
build: fix introduced post-merge build break with no-useless-empty-export
feat(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.5
docs(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/eslint-plugin-tslint (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.0
build: fix introduced post-merge build break with no-useless-empty-export
feat(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.5
docs(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.0
build: fix introduced post-merge build break with no-useless-empty-export
feat(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.5
docs(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