Update dependency @typescript-eslint/parser to v7.14.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typescript-eslint/parser (source)	7.7.1 -> 7.14.1

---

Release Notes

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

v7.14.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.14.0

Compare Source

🚀 Features

• support TypeScript 5.5

❤️ Thank You

• Brad Zacher
• cm-ayf
• Jake Bailey
• James Zhan
• Joshua Chen
• yoshi2no

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

v7.13.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.13.0

Compare Source

🚀 Features

• parser, typescript-estree: export withoutProjectParserOptions utility

❤️ Thank You

• Fotis Papadogeorgopoulos
• Joshua Chen
• Kirk Waiblinger
• Tobiloba Adedeji
• Vinccool96
• YeonJuan

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

v7.12.0

Compare Source

🩹 Fixes

• types: correct typing ParserOptions

❤️ Thank You

• Abraham Guo
• Han Yeong-woo
• Joshua Chen
• Kim Sang Du
• Kirk Waiblinger
• YeonJuan

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

v7.11.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.10.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.9.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.8.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 - "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 26a75fd and detected 0 issues on this pull request.

View more on Code Climate.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @croct/json@0.0.0-dev
npm error Found: eslint@9.2.0
npm error node_modules/eslint
npm error   dev eslint@"^9.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.8.0
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.8.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-09T07_45_07_287Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-09T07_45_07_287Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @croct/json@0.0.0-dev
npm error Found: eslint@9.5.0
npm error node_modules/eslint
npm error   dev eslint@"^9.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.14.1
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.14.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-27T16_12_09_999Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-27T16_12_09_999Z-debug-0.log