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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update nest monorepo to v10.4.12 #14247

Merged
merged 1 commit into from
Dec 3, 2024
Merged

fix(deps): update nest monorepo to v10.4.12 #14247

merged 1 commit into from
Dec 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 29, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nestjs/common (source) 10.4.11 -> 10.4.12 age adoption passing confidence
@nestjs/core (source) 10.4.11 -> 10.4.12 age adoption passing confidence
@nestjs/microservices (source) 10.4.11 -> 10.4.12 age adoption passing confidence
@nestjs/platform-fastify (source) 10.4.11 -> 10.4.12 age adoption passing confidence
@nestjs/platform-socket.io (source) 10.4.11 -> 10.4.12 age adoption passing confidence
@nestjs/testing (source) 10.4.11 -> 10.4.12 age adoption passing confidence

Release Notes

nestjs/nest (@​nestjs/common)

v10.4.12

Compare Source

v10.4.12 (2024-11-29)
Bug fixes
Dependencies
Committers: 1

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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Nov 29, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Nov 29, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts 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: sample/30-event-emitter/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.4.12" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/event-emitter
npm ERR!       @nestjs/event-emitter@"2.0.3" from the root project
npm ERR!     3 more (@nestjs/core, @nestjs/platform-express, @nestjs/testing)
npm ERR!   1 more (@nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/event-emitter
npm ERR!   @nestjs/event-emitter@"2.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/event-emitter
npm ERR!     @nestjs/event-emitter@"2.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-29T13_54_17_760Z-debug-0.log
File name: sample/27-scheduling/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.4.12" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/schedule
npm ERR!       @nestjs/schedule@"4.0.0" from the root project
npm ERR!     3 more (@nestjs/core, @nestjs/platform-express, @nestjs/testing)
npm ERR!   1 more (@nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/schedule
npm ERR!   @nestjs/schedule@"4.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/schedule
npm ERR!     @nestjs/schedule@"4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-29T13_54_24_179Z-debug-0.log
File name: sample/20-cache/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.4.12" from the root project
npm ERR!     peer @nestjs/common@"^9.0.0 || ^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/cache-manager
npm ERR!       @nestjs/cache-manager@"2.2.0" from the root project
npm ERR!     3 more (@nestjs/core, @nestjs/platform-express, @nestjs/testing)
npm ERR!   1 more (@nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/cache-manager
npm ERR!   @nestjs/cache-manager@"2.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/cache-manager
npm ERR!     @nestjs/cache-manager@"2.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-29T13_54_30_535Z-debug-0.log
File name: sample/13-mongo-typeorm/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   reflect-metadata@"^0.2.1" from [email protected]
npm ERR!   node_modules/typeorm
npm ERR!     typeorm@"0.3.20" from the root project
npm ERR!     peer typeorm@"^0.3.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/typeorm
npm ERR!       @nestjs/typeorm@"10.0.1" from the root project
npm ERR!   2 more (@nestjs/common, @nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/typeorm
npm ERR!   @nestjs/typeorm@"10.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/typeorm
npm ERR!     @nestjs/typeorm@"10.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-29T13_54_35_648Z-debug-0.log
File name: sample/07-sequelize/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"*" from [email protected]
npm ERR!   node_modules/sequelize-typescript
npm ERR!     sequelize-typescript@"2.1.6" from the root project
npm ERR!     peer sequelize-typescript@"^2.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/sequelize
npm ERR!       @nestjs/sequelize@"10.0.0" from the root project
npm ERR!   2 more (@nestjs/common, @nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-29T13_54_42_452Z-debug-0.log
File name: sample/05-sql-typeorm/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.2" from the root project
npm ERR!   reflect-metadata@"^0.2.1" from [email protected]
npm ERR!   node_modules/typeorm
npm ERR!     typeorm@"0.3.20" from the root project
npm ERR!     peer typeorm@"^0.3.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/typeorm
npm ERR!       @nestjs/typeorm@"10.0.1" from the root project
npm ERR!   2 more (@nestjs/common, @nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/typeorm
npm ERR!   @nestjs/typeorm@"10.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/typeorm
npm ERR!     @nestjs/typeorm@"10.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-29T13_54_49_092Z-debug-0.log

@coveralls
Copy link

coveralls commented Nov 29, 2024 •
edited
Loading

Pull Request Test Coverage Report for Build b5a57d5d-41e6-41c5-857a-0d36ac68db25

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 91.932%
Totals Coverage Status
Change from base Build f696b4b4-02b7-4b03-bd63-c077a97db9f0: 0.0%
Covered Lines: 6814
Relevant Lines: 7412
💛 - Coveralls

@renovate renovate bot force-pushed the renovate/nest-monorepo branch from bf8fe60 to d0fe483 Compare December 1, 2024 19:17
@renovate renovate bot changed the title chore(deps): update nest monorepo fix(deps): update nest monorepo to v10.4.12 Dec 1, 2024
@kamilmysliwiec kamilmysliwiec merged commit 9b0cd52 into master Dec 3, 2024
5 checks passed
@renovate renovate bot deleted the renovate/nest-monorepo branch December 3, 2024 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Tomyh99095 Tomyh99095 Tomyh99095 approved these changes

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@coveralls @Tomyh99095 @kamilmysliwiec