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 #14

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@typescript-eslint/eslint-plugin (source) 7.16.1 -> 7.18.0 age adoption passing confidence
@typescript-eslint/parser (source) 7.16.1 -> 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.

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.


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 force-pushed the renovate/typescript-eslint-monorepo branch from 430985b to 8d0353c Compare July 23, 2024 02:32
@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 29, 2024
Copy link
Contributor Author

renovate bot commented Aug 6, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^7.15.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/typescript-eslint-monorepo branch August 6, 2024 16:27
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.

1 participant