Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update nestjs (major) #2261

Merged
merged 2 commits into from
Jan 30, 2025
Merged

fix(deps): update nestjs (major) #2261

merged 2 commits into from
Jan 30, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 29, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nestjs/cli ^10.4.9 -> ^11.0.0 age adoption passing confidence
@nestjs/common (source) ^10.4.15 -> ^11.0.0 age adoption passing confidence
@nestjs/config ^3.3.0 -> ^4.0.0 age adoption passing confidence
@nestjs/core (source) ^10.4.15 -> ^11.0.0 age adoption passing confidence
@nestjs/platform-express (source) ^10.4.15 -> ^11.0.0 age adoption passing confidence
@nestjs/schematics ^10.2.3 -> ^11.0.0 age adoption passing confidence
@nestjs/swagger ^8.1.0 -> ^11.0.0 age adoption passing confidence
@nestjs/testing (source) ^10.4.15 -> ^11.0.0 age adoption passing confidence

Release Notes

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

v11.0.2

Compare Source

  • fix: swc compiler does not watch files (8aaa9df)

v11.0.1

Compare Source

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

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/nest (@​nestjs/platform-express)

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

v11.0.0

Compare Source

Release 11.0.0 (2025-01-17)
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.2

Compare Source

Changelog

v11.0.1

Compare Source

11.0.1 (2025-01-17)

Dependencies

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
Dependencies
Committers: 2
nestjs/nest (@​nestjs/testing)

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


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:

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

After merge, new images are deployed in:

@renovate renovate bot enabled auto-merge (squash) January 29, 2025 13:24
Copy link
Contributor Author

renovate bot commented Jan 29, 2025

⚠️ 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   6 more (nest-winston, @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/common
npm error   @nestjs/common@"^11.0.0" from the root project
npm error   peer @nestjs/common@"^5.0.0 || ^6.6.0 || ^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0 || ^11.0.0" from [email protected]
npm error   node_modules/nest-winston
npm error     nest-winston@"^1.10.1" from the root project
npm error   5 more (@nestjs/config, @nestjs/core, ...)
npm error
npm error Could not resolve dependency:
npm error peer @nestjs/common@"^9.0.0 || ^10.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/common
npm error   peer @nestjs/common@"^9.0.0 || ^10.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-29T13_24_10_490Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-29T13_24_10_490Z-debug-0.log

@DerekRoberts DerekRoberts self-assigned this Jan 30, 2025
@DerekRoberts DerekRoberts force-pushed the renovate/major-nestjs branch from c600143 to 96d3480 Compare January 30, 2025 03:10
Copy link
Contributor Author

renovate bot commented Jan 30, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate bot merged commit 2a56a9b into main Jan 30, 2025
26 checks passed
@renovate renovate bot deleted the renovate/major-nestjs branch January 30, 2025 03:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant