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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nestjs/cli	10.4.9 -> 11.0.4
@nestjs/common (source)	10.4.15 -> 11.0.10
@nestjs/core (source)	10.4.15 -> 11.0.10
@nestjs/schematics	10.2.3 -> 11.0.1
@nestjs/terminus	^10.3.0 -> ^11.0.0
@nestjs/testing (source)	10.4.15 -> 11.0.10

---

Release Notes

nestjs/nest-cli (@​nestjs/cli)

v11.0.4

Compare Source

• chore(deps): allow any schematics package newer or eq to v11 (5d79adf)
• chore(deps): update dependency @​swc/core to v1.10.17 (887fa7d)

v11.0.3

Compare Source

• fix(deps): update angular-cli monorepo to v19.1.7 (c8c8904)
• fix(deps): update dependency ansis to v3.15.0 (72d59e1)
• fix(deps): update dependency @​inquirer/prompts to v7.3.2 (ea34a79)
• fix(deps): update dependency webpack to v5.98.0 (24014fc)

v11.0.2

Compare Source

• fix: swc compiler does not watch files (8aaa9df)

v11.0.1

Compare Source

• fix: pass matched paths to chokidar watcher (watchAssets) (bd96064)
  • issue ref: https://github.com/nestjs/nest/issues/14463

v11.0.0

Compare Source

Migration guide: https://docs.nestjs.com/migration-guide

Features and improvements

• feat(schematics): list schematics from extended collections #​2096
• feat: nest build --all flag #​2312
• feat: add flag to disable shell mode for nest start --watch #​2522
• feat!: drop uncommon variants of nest cli config file name #​2769
• feat: add support for --env-file flag #​2818

Dependencies

• fix(deps): update dependency glob to v11 #​2788
• chore/upgrade inquirer package #​2718
• fix(deps): update dependency chokidar to v4 #​2734
• fix(deps): update angular-cli monorepo to v19 #​2811

nestjs/nest (@​nestjs/common)

v11.0.10

Compare Source

v11.0.10 (2025-02-17)

Bug fixes

• microservices
  • #​14605 fix(microservices): server send drops emitted value (@​shprota)
• platform-express
  • https://github.com/nestjs/nest/pull/14640 fix(platform-express) respect custom parser middlewares in Express 5 (@​luddwichr)

v11.0.9

Compare Source

v11.0.9 (2025-02-10)

Bug fixes

• core
  • #​14597 perf(core): use topology tree for calculating distance (depth) (@​kamilmysliwiec)
• common
  • #​14579 fix(common): revert to original value (swc builders regression) (@​kamilmysliwiec)

Committers: 2

• Kamil Mysliwiec (@​kamilmysliwiec)

v11.0.8

Compare Source

v11.0.8 (2025-02-06)

Bug fixes

• common
  • #​14546 fix(common): addLeadingSlash optional group support (@​dcharbonnier)
• platform-express
  • #​14574 fix(platform-express) make check for existing middlewares work with Express 5 (@​luddwichr)

Committers: 4

• Ghassen Rjab (@​GhassenRjab)
• Shay Molcho (@​shaymolcho)
• @​dcharbonnier
• @​luddwichr

v11.0.7

Compare Source

v11.0.7 (2025-01-31)

Bug fixes

• core
  • #​14523 fix: middleware sort issues (@​rbnayax)

Committers: 1

• @​rbnayax

v11.0.6

Compare Source

v11.0.6 (2025-01-27)

Bug fixes

• core
  • #​14522 fix(core): allow optional named wildcard groups (@​kamilmysliwiec)

Committers: 1

• Kamil Mysliwiec (@​kamilmysliwiec)

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

Compare Source

• fix(deps): update angular-cli monorepo to v19.1.7 (a532fd8)
• chore: update typescript compiler target (83f92d0)

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 - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15732963	Triggered	Generic Password	6ec5cdb	pnpm-lock.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue