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 tsconfig-paths to v4.2.0 #11518

Merged
merged 1 commit into from
Apr 18, 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
tsconfig-paths 4.0.0 -> 4.2.0 age adoption passing confidence
tsconfig-paths 4.1.2 -> 4.2.0 age adoption passing confidence

Release Notes

dividab/tsconfig-paths

v4.2.0

Compare Source

Added

v4.1.2

Compare Source

Fixed

v4.1.1

Compare Source

Fixed
  • Skip stat call / throwing an exception when source files don't exist. See PR #​225. Thanks to @​robstolarz for this PR!

v4.1.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 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 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: 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/a488b0/48935f/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/a488b0/48935f/cache/others/npm/_logs/2023-04-17T12_14_39_995Z-debug-0.log

@coveralls
Copy link

Pull Request Test Coverage Report for Build 914700aa-3035-41a0-9cbc-5fe9cb9a8a9d

  • 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.675%

Totals Coverage Status
Change from base Build f23345a9-4bf0-40c2-8532-76451fb44463: 0.0%
Covered Lines: 6516
Relevant Lines: 7031

💛 - Coveralls

@kamilmysliwiec kamilmysliwiec merged commit 50282e9 into master Apr 18, 2023
@delete-merged-branch delete-merged-branch bot deleted the renovate/tsconfig-paths-4.x branch April 18, 2023 08:03
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