Support NestJS 11

[xballoy]

Support NestJS v11:

• add NestJS 11 in package's peerDependencies
• bump @Angular-devkit to v19: required with @nestjs/schematics see https://github.com/nestjs/schematics/releases/tag/11.0.0

Fixes #1215

[changeset-bot]

🦋 Changeset detected

Latest commit: ce3d4f4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
nest-commander-schematics	Minor
nest-commander-testing	Minor
nest-commander	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

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

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15197365	Triggered	Generic Password	306b01e	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.}

[xballoy]

Note

Must be the same version than the one in @nestjs/schematics to prevent typing issues.

[xballoy]

Note

I specified a minor change but I can change to major if you think this is needed.

[jmcdo29]

Thank you! Been hectic since the release, so I appreciate someone helping out with this!