fix(deps): update nest monorepo to v11 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nestjs/common (source)	^10.4.15 -> ^11.0.0
@nestjs/core (source)	^10.4.15 -> ^11.0.0
@nestjs/microservices (source)	^10.4.15 -> ^11.0.0
@nestjs/platform-express (source)	^10.4.15 -> ^11.0.0
@nestjs/schematics	^10.2.3 -> ^11.0.0
@nestjs/terminus	^10.3.0 -> ^11.0.0
@nestjs/testing (source)	^10.4.15 -> ^11.0.0

---

Release Notes

nestjs/nest (@​nestjs/common)

v11.0.5

Compare Source

v11.0.5 (2025-01-23)

Bug fixes

• core
  • #​14495 fix(core): global module middleware should be executed first (@​kamilmysliwiec)

Committers: 1

• Kamil Mysliwiec (@​kamilmysliwiec)

v11.0.4

Compare Source

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

nestjs/schematics (@​nestjs/schematics)

v11.0.0

Compare Source

Release 11.0.0 (2025-01-17)

• NestJS v11 (migration guide https://docs.nestjs.com/migration-guide)
• ESLint v9
• Angular Devkit Schematics v19

Changelog

• feat: sort library and sub-app names to reduce git merge conflicts (797a384)
• feat: enable strict null checks and consistent casing (a4cb235)
• chore: upgrade to eslint v9 (7b205f5)

nestjs/terminus (@​nestjs/terminus)

v11.0.0

Compare Source

---

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 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 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/common
npm error   @nestjs/common@"^11.0.0" from the root project
npm error   peer @nestjs/common@"^10.0.0 || ^11.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/bull-shared
npm error     @nestjs/bull-shared@"^11.0.2" from @nestjs/[email protected]
npm error     node_modules/@nestjs/bullmq
npm error       @nestjs/bullmq@"^11.0.2" from the root project
npm error   11 more (@nestjs/bullmq, @nestjs/config, @nestjs/cqrs, ...)
npm error
npm error Could not resolve dependency:
npm error peer @nestjs/common@"^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/axios
npm error   @nestjs/axios@"^3.1.3" from the root project
npm error   peerOptional @nestjs/axios@"^2.0.0 || ^3.0.0 || ^4.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/terminus
npm error     @nestjs/terminus@"^11.0.0" from the root project
npm error
npm error Conflicting peer dependency: @nestjs/[email protected]
npm error node_modules/@nestjs/common
npm error   peer @nestjs/common@"^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/axios
npm error     @nestjs/axios@"^3.1.3" from the root project
npm error     peerOptional @nestjs/axios@"^2.0.0 || ^3.0.0 || ^4.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/terminus
npm error       @nestjs/terminus@"^11.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-02-20T20_42_54_836Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-02-20T20_42_54_836Z-debug-0.log