chore(deps): update nestjs packages (fastify) (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nestjs/cache-manager	^2.2.2 -> ^2.2.2 || ^3.0.0
@nestjs/cache-manager	2.3.0 -> 3.0.0
@nestjs/common (source)	10.4.15 -> 11.0.5
@nestjs/config	3.3.0 -> 4.0.0
@nestjs/core (source)	10.4.15 -> 11.0.5
@nestjs/platform-express (source)	10.4.15 -> 11.0.5
@nestjs/testing (source)	10.4.15 -> 11.0.5

---

Release Notes

nestjs/cache-manager (@​nestjs/cache-manager)

v3.0.0

Compare Source

Breaking changes

@nestjs/cache-manager v3 does no longer support cache-manager < v6. Migration to Keyv is necessary.

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

Changelog

• chore(deps): support cache-manager v6 (94c9373)
• chore(deps): update dependency cache-manager to v6 (df48080)

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)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

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

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

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @anchan828/nest-cache-packages@0.0.0
npm error Found: cache-manager@5.7.6
npm error node_modules/cache-manager
npm error   dev cache-manager@"5.7.6" from the root project
npm error   peerOptional cache-manager@"*" from @nestjs/microservices@11.0.5
npm error   node_modules/@nestjs/microservices
npm error     peerOptional @nestjs/microservices@"^11.0.0" from @nestjs/core@11.0.5
npm error     node_modules/@nestjs/core
npm error       dev @nestjs/core@"11.0.5" from the root project
npm error       4 more (@nestjs/cache-manager, @nestjs/microservices, ...)
npm error   5 more (@anchan828/nest-cache, @anchan828/nest-cache-common, ...)
npm error
npm error Could not resolve dependency:
npm error peer cache-manager@">=6" from @nestjs/cache-manager@3.0.0
npm error node_modules/@nestjs/cache-manager
npm error   dev @nestjs/cache-manager@"3.0.0" from the root project
npm error   dev @nestjs/cache-manager@"3.0.0" from @anchan828/nest-cache@3.1.28
npm error   packages/cache
npm error     @anchan828/nest-cache@3.1.28
npm error     node_modules/@anchan828/nest-cache
npm error       workspace packages/cache 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-26T08_57_48_075Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-26T08_57_48_075Z-debug-0.log