fix(deps): update dependency @nestjs/mongoose to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@nestjs/mongoose	^10.0.0 -> ^11.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

nestjs/mongoose (@​nestjs/mongoose)

v11.0.3

Compare Source

What's Changed

• fix: populate on arrays by @​schw4rzlicht in #​2438

New Contributors

• @​schw4rzlicht made their first contribution in #​2438

Full Changelog: nestjs/mongoose@11.0.2...11.0.3

v11.0.2

Compare Source

• feat: Add ObjectId validation & parsing pipes (f3d3d25)

v11.0.1

Compare Source

What's Changed

• feat: inherit virtuals from parent classes by @​kamilmysliwiec in #​2379

Full Changelog: nestjs/mongoose@11.0.0...11.0.1

v11.0.0

Compare Source

• chore(deps): update nest monorepo to v11 (d675794)

---

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 this update 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/[email protected]
npm error Found: @nestjs/[email protected]
npm error node_modules/@nestjs/mongoose
npm error   @nestjs/mongoose@"^11.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @nestjs/mongoose@"^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/terminus
npm error   @nestjs/terminus@"^10.0.0" from the root project
npm error
npm error Conflicting peer dependency: @nestjs/[email protected]
npm error node_modules/@nestjs/mongoose
npm error   peerOptional @nestjs/mongoose@"^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/terminus
npm error     @nestjs/terminus@"^10.0.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 /runner/cache/others/npm/_logs/2025-12-02T05_57_29_216Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-02T05_57_29_216Z-debug-0.log