chore(deps): update typescript-eslint monorepo to v8.34.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typescript-eslint/eslint-plugin (source)	8.34.0 -> 8.34.1
@typescript-eslint/parser (source)	8.34.0 -> 8.34.1
typescript-eslint (source)	8.34.0 -> 8.34.1

---

Release Notes

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

v8.34.1

Compare Source

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

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

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

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

typescript-eslint/typescript-eslint (typescript-eslint)

v8.34.1

Compare Source

This was a version bump only for typescript-eslint 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: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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]

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/common@11.0.16
npm error Found: file-type@21.0.0
npm error node_modules/file-type
npm error   file-type@"21.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer file-type@"^20.4.1" from @nestjs/common@11.0.16
npm error node_modules/@nestjs/common
npm error   peer @nestjs/common@"^11.0.1" from @nestjs/apollo@13.1.0
npm error   node_modules/@nestjs/apollo
npm error     dev @nestjs/apollo@"13.1.0" from the root project
npm error   peer @nestjs/common@"^11.0.0" from @nestjs/core@11.0.3
npm error   node_modules/@nestjs/core
npm error     peer @nestjs/core@"^11.0.1" from @nestjs/apollo@13.1.0
npm error     node_modules/@nestjs/apollo
npm error       dev @nestjs/apollo@"13.1.0" from the root project
npm error     3 more (@nestjs/graphql, @nestjs/mongoose, @nestjs/typeorm)
npm error   4 more (@nestjs/graphql, @nestjs/mapped-types, ...)
npm error
npm error Conflicting peer dependency: file-type@20.5.0
npm error node_modules/file-type
npm error   peer file-type@"^20.4.1" from @nestjs/common@11.0.16
npm error   node_modules/@nestjs/common
npm error     peer @nestjs/common@"^11.0.1" from @nestjs/apollo@13.1.0
npm error     node_modules/@nestjs/apollo
npm error       dev @nestjs/apollo@"13.1.0" from the root project
npm error     peer @nestjs/common@"^11.0.0" from @nestjs/core@11.0.3
npm error     node_modules/@nestjs/core
npm error       peer @nestjs/core@"^11.0.1" from @nestjs/apollo@13.1.0
npm error       node_modules/@nestjs/apollo
npm error         dev @nestjs/apollo@"13.1.0" from the root project
npm error       3 more (@nestjs/graphql, @nestjs/mongoose, @nestjs/typeorm)
npm error     4 more (@nestjs/graphql, @nestjs/mapped-types, ...)
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 /runner/cache/others/npm/_logs/2025-06-17T08_45_04_672Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-17T08_45_04_672Z-debug-0.log

[coveralls]

Pull Request Test Coverage Report for Build 4ded094f-4f38-4611-9431-9144a6c9933b

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 88.918%

---

Totals
Change from base Build 5e88f11f-c810-4b23-8e7d-3f0d6939e428:	0.0%
Covered Lines:	7197
Relevant Lines:	8094

---

💛 - Coveralls