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

chore(deps): update typescript-eslint monorepo to v7.18.0 #380

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@typescript-eslint/eslint-plugin (source) 7.15.0 -> 7.18.0 age adoption passing confidence
@typescript-eslint/parser (source) 7.15.0 -> 7.18.0 age adoption passing confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.18.0

Compare Source

🩹 Fixes
  • eslint-plugin: [no-unnecessary-type-assertion] prevent runtime error when asserting a variable declared in default TS lib

  • eslint-plugin: [unbound-method] report on destructuring in function parameters

  • eslint-plugin: [no-duplicate-type-constituents] shouldn't report on error types

  • eslint-plugin: [strict-boolean-expressions] support branded booleans

❤️ Thank You
  • auvred
  • Oliver Salzburg
  • Vinccool96
  • Yukihiro Hasegawa

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

v7.17.0

Compare Source

🚀 Features
  • eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7

  • eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never"

🩹 Fixes
  • eslint-plugin: [no-floating-promises] check top-level type assertions (and more)

  • eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context

  • eslint-plugin: [no-unnecessary-condition] false positive on optional private field

❤️ Thank You
  • Armano
  • Josh Goldberg ✨
  • Kirk Waiblinger
  • StyleShit

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

v7.16.1

Compare Source

🩹 Fixes
  • eslint-plugin: [no-unnecessary-type-parameters] descend into all parts of mapped types in no-unnecessary-type-parameters
❤️ Thank You
  • Dan Vanderkam

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

v7.16.0

Compare Source

🚀 Features
  • rule-tester: stricter rule test validations

  • eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule

  • eslint-plugin: add support for nested namespaces to unsafe-member-access

  • eslint-plugin: [no-floating-promises] add checkThenables option

🩹 Fixes
  • deps: update dependency @​eslint-community/regexpp to v4.11.0

  • eslint-plugin: [no-floating-promises] add suggestions to tests from #​9263 checkThenables

  • website: react key error on internal pages of website

  • eslint-plugin: [restrict-template-expressions] don't report tuples if allowArray option is enabled

❤️ Thank You
  • Abraham Guo
  • auvred
  • Josh Goldberg ✨
  • Juan Sanchez
  • Vinccool96
  • YeonJuan
  • Yukihiro Hasegawa

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

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.18.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

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

v7.17.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

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

v7.16.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

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

v7.16.0

Compare Source

🩹 Fixes
❤️ Thank You
  • Abraham Guo
  • auvred
  • Josh Goldberg ✨
  • Juan Sanchez
  • Vinccool96
  • YeonJuan
  • Yukihiro Hasegawa

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v7.16.0 chore(deps): update typescript-eslint monorepo to v7.16.1 Jul 18, 2024
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch 2 times, most recently from 939ef23 to 433ae67 Compare July 23, 2024 23:28
@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v7.16.1 chore(deps): update typescript-eslint monorepo to v7.17.0 Jul 23, 2024
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from 433ae67 to 9f55310 Compare July 30, 2024 08:52
@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v7.17.0 chore(deps): update typescript-eslint monorepo to v7.18.0 Jul 30, 2024
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from 9f55310 to 2a1eae0 Compare October 9, 2024 07:35
Copy link
Contributor Author

renovate bot commented Nov 29, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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

Successfully merging this pull request may close these issues.

0 participants