fix(deps): update nestjs (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nestjs/axios	^3.0.2 -> ^4.0.0
@nestjs/cli	^10.3.2 -> ^11.0.0
@nestjs/common (source)	^10.3.8 -> ^11.0.0
@nestjs/config	^3.2.2 -> ^4.0.0
@nestjs/core (source)	^10.3.8 -> ^11.0.0
@nestjs/platform-express (source)	^10.3.8 -> ^11.0.0
@nestjs/schedule	^4.0.2 -> ^5.0.0
@nestjs/schematics	^10.1.1 -> ^11.0.0
@nestjs/swagger	^8.0.0 -> ^11.0.0
@nestjs/testing (source)	^10.3.8 -> ^11.0.0

---

Release Notes

nestjs/axios (@​nestjs/axios)

v4.0.0

Compare Source

What's Changed

• chore(deps): update nest monorepo to v11 (major) by @​renovate in https://github.com/nestjs/axios/pull/1296

Full Changelog: nestjs/axios@3.1.3...4.0.0

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

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.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/config (@​nestjs/config)

v4.0.0

Compare Source

Breaking changes

The order in which configuration variables are read by the ConfigService#get method has been updated. The new order is:

• Internal configuration (config namespaces and custom config files)
• Validated environment variables (if validation is enabled and a schema is provided)
• The process.env object

Previously, validated environment variables and the process.env object were read first, preventing them from being overridden by internal configuration. With this update, internal configuration will now always take precedence over environment variables.

Additionally, the ignoreEnvVars configuration option, which previously allowed disabling validation of the process.env object, has been deprecated. Instead, use the validatePredefined option (set to false to disable validation of predefined environment variables). Predefined environment variables refer to process.env variables that were set before the module was imported. For example, if you start your application with PORT=3000 node main.js, the PORT variable is considered predefined. However, variables loaded by the ConfigModule from a .env file are not classified as predefined.

A new skipProcessEnv option has also been introduced. This option allows you to prevent the ConfigService#get method from accessing the process.env object entirely, which can be helpful when you want to restrict the service from reading environment variables directly.

Changelog

• chore: update config attributes to more self descriptive names (c2eaf04)
• chore(deps): update nest monorepo to v11 (1c20713)
• feat: order of reading variables, add skip predefined (c53c63c)

nestjs/schedule (@​nestjs/schedule)

v5.0.1

Compare Source

What's Changed

• feat: add waitForCompletion for cronjobs to disable concurrent running cronjobs by @​thomaschaaf in https://github.com/nestjs/schedule/pull/1870

New Contributors

• @​thomaschaaf made their first contribution in https://github.com/nestjs/schedule/pull/1870

Full Changelog: nestjs/schedule@5.0.0...5.0.1

v5.0.0

Compare Source

Breaking changes

• requires Node >= v20

Changelog

• fix(deps): update dependency cron to v3.5.0 (ae6c43c)
• chore(deps): update nest monorepo to v11 (41d8cdb)
• chore(deps): Use crypto.randomUUID() instead of uuid module (58f795d)

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/swagger (@​nestjs/swagger)

v11.0.3

Compare Source

11.0.3 (2025-01-23)

Bug fixes

• #​3264 fix: incorrect IsUuid class-validator decorator (@​degradingsky746)

Committers: 1

• Fozail (@​degradingsky746)

v11.0.2

Compare Source

Changelog

• Revert "feat: make generated require() ESM compatible https://github.com/nestjs/swagger/pull/3253

v11.0.1

Compare Source

11.0.1 (2025-01-17)

Dependencies

• #​3249 fix(deps): update dependency @​nestjs/mapped-types to v2.1.0 (@​renovate[bot])

v11.0.0

Compare Source

11.0.0 (2025-01-16)

Breaking changes

This version is only compatible with @nestjs/{core,common,platform-express,platform-fastify,...} >= v11

Enhancements

• #​3199 release: version 11.0.0 (@​kamilmysliwiec)
• #​3235 feat: make generated require() ESM compatible (@​bdezso)

Dependencies

• #​3080 chore(deps): update dependency @​fastify/static to v8.0.4 (@​renovate[bot])
• #​3245 chore(deps): update dependency fastify to v5.2.1 (@​renovate[bot])

Committers: 2

• Bence Dezso (@​bdezso)
• Kamil Mysliwiec (@​kamilmysliwiec)

v8.1.1

Compare Source

Unreleased (2025-01-10)

Bug fixes

• #​3232 fix: missing ApiProperty enum undefined handling (@​nxht)
• #​3223 fix: swagger crashed while using any Param/Query/Body decorator in a monorepo with pnpm (@​winuxx)

Dependencies

• #​3230 chore(deps): update dependency typescript to v5.7.3 (@​renovate[bot])
• #​3201 chore(deps): update nest monorepo to v10.4.15 (@​renovate[bot])
• #​3200 chore(deps): update dependency express to v4.21.2 (@​renovate[bot])

Committers: 3

• Mak (@​Makkalay)
• @​winuxx
• hgpark (@​nxht)

---

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.

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[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: backend/package-lock.json

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @nestjs/[email protected]
npm warn Found: @nestjs/[email protected]
npm warn node_modules/@nestjs/common
npm warn   @nestjs/common@"^11.0.0" from the root project
npm warn   7 more (@nestjs/axios, @nestjs/config, @nestjs/core, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm warn node_modules/@nestjs/mapped-types
npm warn
npm warn Conflicting peer dependency: @nestjs/[email protected]
npm warn node_modules/@nestjs/common
npm warn   peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm warn   node_modules/@nestjs/mapped-types
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/axios
npm error   @nestjs/axios@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @nestjs/axios@"^1.0.0 || ^2.0.0 || ^3.0.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/terminus
npm error   @nestjs/terminus@"^10.2.3" from the root project
npm error
npm error Conflicting peer dependency: @nestjs/[email protected]
npm error node_modules/@nestjs/axios
npm error   peerOptional @nestjs/axios@"^1.0.0 || ^2.0.0 || ^3.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/terminus
npm error     @nestjs/terminus@"^10.2.3" 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 /tmp/renovate/cache/others/npm/_logs/2025-01-30T19_59_48_362Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-30T19_59_48_362Z-debug-0.log