fix(deps): update nest monorepo (patch) - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nestjs/cli	11.0.2 -> 11.0.4
@nestjs/common (source)	11.0.9 -> 11.0.10
@nestjs/core (source)	11.0.9 -> 11.0.10
@nestjs/platform-fastify (source)	11.0.9 -> 11.0.10
@nestjs/platform-socket.io (source)	11.0.9 -> 11.0.10
@nestjs/schematics	11.0.0 -> 11.0.1
@nestjs/testing (source)	11.0.9 -> 11.0.10
@nestjs/websockets (source)	11.0.9 -> 11.0.10

---

Release Notes

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

v11.0.4

Compare Source

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)

nestjs/nest (@​nestjs/common)

v11.0.10

Compare Source

nestjs/nest (@​nestjs/core)

v11.0.10

Compare Source

nestjs/nest (@​nestjs/platform-fastify)

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)

nestjs/schematics (@​nestjs/schematics)

v11.0.1

Compare Source

nestjs/nest (@​nestjs/testing)

v11.0.10

Compare Source

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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
15682783	Triggered	Generic Password	99898a1	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.}