Update dependency @typescript-eslint/parser to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typescript-eslint/parser (source)	^6.0.0 -> ^7.0.0

---

Release Notes

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

v7.4.0

Compare Source

v7.3.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.3.0

Compare Source

🩹 Fixes

• correct engines.node constraints in package.json

❤️ Thank You

• Abraham Guo
• Alexu
• Arka Pratim Chaudhuri
• auvred
• Derrick Isaacson
• fnx
• Josh Goldberg ✨
• Kirk Waiblinger
• Marta Cardoso
• Michaël De Boey
• Tristan Rasmussen
• YeonJuan

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

v7.2.0

Compare Source

🚀 Features

• support TS 5.4

❤️ Thank You

• Arka Pratim Chaudhuri
• auvred
• Chris Plummer
• Fotis Papadogeorgopoulos
• Josh Goldberg ✨
• Kirk Waiblinger
• Wayne Zhang
• YeonJuan

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

v7.1.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.1.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.0.2

Compare Source

🩹 Fixes

• fix tsconfig-less check errors, fix @types/eslint incompatibilities, add tests

❤️ Thank You

• Brad Zacher
• Gareth Jones

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

v7.0.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.0.0

Compare Source

🚀 Features

• ⚠️ bump ESLint, NodeJS, and TS minimum version requirements

• add support for flat configs

⚠️ Breaking Changes

• ⚠️ bump ESLint, NodeJS, and TS minimum version requirements

❤️ Thank You

• Brad Zacher
• Kirk Waiblinger
• StyleShit
• YeonJuan

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

6.21.0 (2024-02-05)

🚀 Features

• allow parserOptions.project: false

❤️ Thank You

• auvred
• Brad Zacher
• Kirk Waiblinger
• Pete Gonzalez
• YeonJuan

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

6.20.0 (2024-01-29)

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.

6.19.1 (2024-01-22)

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.

6.19.0 (2024-01-15)

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.

6.18.1 (2024-01-08)

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.

6.18.0 (2024-01-06)

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 - "before 4am on the first day of the month" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

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

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

👋 @renovate[bot]
Thanks for your contribution!
The approval and merge process is almost fully automated 🧙
Here's how it works:

1. You open a new pull request
2. Automated tests check the code
3. Maintainers review the code
4. Once approved, the PR is ready to merge.

👉 Omit the extended description
Please remove the commit body before merging the pull request.
Instead, include the pull request number in the title to provide the full context
about the change.

☝️ Lastly, the title for the commit will come from the pull request title. So please provide a descriptive title that summarizes the changes in 50 characters or less using the imperative mood.
Happy coding! 🎉

[codeclimate]

Code Climate has analyzed commit a3ef39f and detected 0 issues on this pull request.

View more on Code Climate.