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

chore(deps): update dependency @types/node to v18.16.17 #11516

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 17, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 18.0.3 -> 18.16.17 age adoption passing confidence
@types/node (source) 18.15.0 -> 18.16.17 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Apr 17, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Apr 17, 2023

⚠ 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/33-graphql-mercurius/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/mercurius@10.0.17
npm ERR! Found: mercurius@12.2.0
npm ERR! node_modules/mercurius
npm ERR!   mercurius@"12.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mercurius@"^8.12.0 || ^9.0.0 || ^10.0.0" from @nestjs/mercurius@10.0.17
npm ERR! node_modules/@nestjs/mercurius
npm ERR!   @nestjs/mercurius@"10.0.17" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mercurius@10.5.1
npm ERR! node_modules/mercurius
npm ERR!   peer mercurius@"^8.12.0 || ^9.0.0 || ^10.0.0" from @nestjs/mercurius@10.0.17
npm ERR!   node_modules/@nestjs/mercurius
npm ERR!     @nestjs/mercurius@"10.0.17" 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/worker/3ffcb8/a6f6ae/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/worker/3ffcb8/a6f6ae/cache/others/npm/_logs/2023-06-12T12_07_49_208Z-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: typeorm@0.3.16
npm ERR! Found: mongodb@3.6.0
npm ERR! node_modules/mongodb
npm ERR!   mongodb@"3.6.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional mongodb@"^5.2.0" from typeorm@0.3.16
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"0.3.16" from the root project
npm ERR!   peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!   node_modules/@nestjs/typeorm
npm ERR!     @nestjs/typeorm@"9.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mongodb@5.6.0
npm ERR! node_modules/mongodb
npm ERR!   peerOptional mongodb@"^5.2.0" from typeorm@0.3.16
npm ERR!   node_modules/typeorm
npm ERR!     typeorm@"0.3.16" from the root project
npm ERR!     peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!     node_modules/@nestjs/typeorm
npm ERR!       @nestjs/typeorm@"9.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/worker/3ffcb8/a6f6ae/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/worker/3ffcb8/a6f6ae/cache/others/npm/_logs/2023-06-12T12_11_00_050Z-debug-0.log

@coveralls
Copy link

coveralls commented Apr 17, 2023

Pull Request Test Coverage Report for Build 4b89cde3-6844-4642-a514-27855d8fc29b

  • 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 92.784%

Totals Coverage Status
Change from base Build 3ece410f-8e19-4af4-acd0-eeebfea591f4: 0.0%
Covered Lines: 6326
Relevant Lines: 6818

💛 - Coveralls

@renovate renovate bot changed the title chore(deps): update dependency @types/node to v18.15.11 chore(deps): update dependency @types/node to v18.16.16 May 28, 2023
@renovate renovate bot force-pushed the renovate/node-18.x branch 3 times, most recently from e4ae004 to 4265acd Compare May 29, 2023 10:07
@renovate renovate bot force-pushed the renovate/node-18.x branch 3 times, most recently from c9a8845 to aff574a Compare June 12, 2023 02:03
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v18.16.16 chore(deps): update dependency @types/node to v18.16.17 Jun 12, 2023
@renovate renovate bot force-pushed the renovate/node-18.x branch 5 times, most recently from 1a42672 to f10bfad Compare June 12, 2023 11:40
@kamilmysliwiec kamilmysliwiec merged commit ea29da1 into master Jun 12, 2023
@delete-merged-branch delete-merged-branch bot deleted the renovate/node-18.x branch June 12, 2023 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants