Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update all of typescript-eslint → 6.21.0 (unknown) #141

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Feb 12, 2024

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​typescript-eslint/eslint-plugin (^5.44.0 → ^6.21.0) · Repo · Changelog

Release Notes

6.21.0

6.21.0 (2024-02-05)

🚀 Features

  • export plugin metadata (#8331)
  • allow parserOptions.project: false (#8339)
  • eslint-plugin: add rule prefer-find (#8216)
  • typescript-estree: forbid duplicated accessibility modifiers (#8257)
  • utils: improve eslint types (#8344)

🩹 Fixes

  • ast-spec: add JSXElement type to the JSXAttribute['value'] (#8285)
  • eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression (#8265)
  • eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values (#8250)
  • eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions (#8332)
  • eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option (#8249)
  • eslint-plugin: [class-literal-property-style] allow getter when same key setter exists (#8277)
  • eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword (#8326)
  • rule-tester: fix a phantom dependency on the "semver" package (#8260)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 51 commits:


Depfu Status

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants