Bump @nestjs/cli from 10.4.8 to 11.0.7
Bumps @nestjs/cli from 10.4.8 to 11.0.7.
Release notes
Sourced from @nestjs/cli's releases.
Release 11.0.7
What's Changed
- fix(deps): update angular-cli monorepo to v19.2.8 by
@renovatein nestjs/nest-cli#2985- chore(deps): update dependency
@swc/clito v0.7.3 by@renovatein nestjs/nest-cli#2994- feat: support multiple
--env-filearguments by@micaleviskin nestjs/nest-cli#3000- fix(deps): update dependency webpack to v5.99.6 by
@renovatein nestjs/nest-cli#2996Full Changelog: https://github.com/nestjs/nest-cli/compare/11.0.6...11.0.7
Release 11.0.6
What's Changed
- fix(deps): update dependency ansis to v3.17.0 by
@renovatein nestjs/nest-cli#2936- chore(deps): update dependency
@swc/coreto v1.11.16 by@renovatein nestjs/nest-cli#2972- style: adjust spacing after heart emoji in package_manager_question by
@RayRemnantin nestjs/nest-cli#2974- fix(deps): update angular-cli monorepo to v19.2.6 by
@renovatein nestjs/nest-cli#2946- fix(deps): update dependency fork-ts-checker-webpack-plugin to v9.1.0 by
@renovatein nestjs/nest-cli#2968- fix(deps): update dependency
@inquirer/promptsto v7.4.1 by@renovatein nestjs/nest-cli#2952New Contributors
@RayRemnantmade their first contribution in nestjs/nest-cli#2974Full Changelog: https://github.com/nestjs/nest-cli/compare/11.0.5...11.0.6
Release 11.0.5
- feat(swc): add reload application when compiling to mjs (d866d777)
Release 11.0.4
- chore(deps): allow any schematics package newer or eq to v11 (5d79adfc)
- chore(deps): update dependency
@swc/coreto v1.10.17 (887fa7d1)Release 11.0.3
- fix(deps): update angular-cli monorepo to v19.1.7 (c8c89042)
- fix(deps): update dependency ansis to v3.15.0 (72d59e19)
- fix(deps): update dependency
@inquirer/promptsto v7.3.2 (ea34a79b)- fix(deps): update dependency webpack to v5.98.0 (24014fc1)
Release 11.0.2
- fix: swc compiler does not watch files (8aaa9df6)
Release 11.0.1
- fix: pass matched paths to chokidar watcher (watchAssets) (bd960640)
- issue ref: nestjs/nest#14463
11.0.0
Migration guide: https://docs.nestjs.com/migration-guide
Features and improvements
... (truncated)
Commits
e343fabchore(): release v11.0.78a0c1c1Merge pull request #2996 from nestjs/renovate/webpack-5.xa6ddad8Merge pull request #3000 from micalevisk/feat/issue-2981c5df8e6refactor: deduplicateassertNonArrayutility function62b2434chore(deps): update typescript-eslint monorepo to v8.31.0 (#2999)36a464dchore(deps): update dependency eslint to v9.25.1 (#2998)bca2918feat: support multiple--env-filearguments7397574chore(deps): update dependency eslint to v9.25.0 (#2997)34467d3fix(deps): update dependency webpack to v5.99.6ec7d02achore(deps): update dependency release-it to v19 (#2995)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
⚠️ 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 | |
|---|---|---|---|---|---|
| 16286400 | Triggered | Generic Password | 68cd9c3c63222071812bca3f4eff79165394fcdb | pnpm-lock.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
Superseded by #202.