subsquid-labs / giant-squid-main

GNU General Public License v3.0
2 stars 5 forks source link

Update dependency @types/node to v20 #175

Open renovate[bot] opened 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate logo banner

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 18.18.13 -> 20.10.0 age adoption passing confidence

Configuration

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

🚦 Automerge: Disabled because a matching PR was automerged previously.

â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 1 year ago

âš  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:

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: kusama-transfers@undefined
npm ERR! Found: typeorm@0.3.16
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"0.3.16" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typeorm@"^0.3.17" from @subsquid/typeorm-migration@1.2.2
npm ERR! node_modules/@subsquid/typeorm-migration
npm ERR!   @subsquid/typeorm-migration@"1.2.2" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/e4188b/831c12/cache/others/npm/_logs/2023-11-24T10_56_31_534Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/e4188b/831c12/cache/others/npm/_logs/2023-11-24T10_56_31_534Z-debug-0.log