Skip to content

chore(deps): update typescript-eslint monorepo to v8.31.0 #182

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

Merged
merged 1 commit into from
Apr 23, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 15, 2025

This PR contains the following updates:

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

Release Notes

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

v8.31.0

Compare Source

🚀 Features
  • eslint-plugin: [no-unnecessary-type-assertion] add option to ignore string const assertions (#​10979)
❤️ Thank You
  • Nicolas Le Cam

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

v8.30.1

Compare Source

🩹 Fixes
  • eslint-plugin: fix mistake with eslintrc config generation (#​11072)
❤️ Thank You

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

v8.30.0

Compare Source

🚀 Features
  • eslint-plugin: [no-explicit-any] suggest to replace keyof any with PropertyKey (#​11032)
🩹 Fixes
  • eslint-plugin: [promise-function-async] use a different error message for functions with promise and non-promise types (#​10950)
❤️ Thank You

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

v8.29.1

Compare Source

🩹 Fixes
  • eslint-plugin: [no-deprecated] report on deprecated imported variable used as property (#​10998)
❤️ Thank You
  • Ronen Amiel

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

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

v8.31.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.

v8.30.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.

v8.30.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.

v8.29.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.


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 310f2a0 to 942070e Compare April 21, 2025 17:38
@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v8.30.1 chore(deps): update typescript-eslint monorepo to v8.31.0 Apr 21, 2025
@jkalandaibm jkalandaibm merged commit 801ba94 into master Apr 23, 2025
4 checks passed
@renovate renovate bot deleted the renovate/typescript-eslint-monorepo branch April 23, 2025 14:39
@MalarvizhiK
Copy link
Member

🎉 This PR is included in version 0.35.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

2 participants