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

Update dependency @subsquid/typeorm-migration to v1 #51

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@subsquid/typeorm-migration 0.1.6 -> 1.3.0 age adoption passing confidence

Release Notes

subsquid/squid (@​subsquid/typeorm-migration)

v1.3.0

Compare Source

v1.2.4

Compare Source

v1.2.3

Compare Source

v1.2.2

Compare Source

v1.2.1

Compare Source

v1.2.0

Compare Source

v1.0.0

Compare Source


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.


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

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

Copy link
Contributor Author

renovate bot commented Mar 2, 2024

⚠ 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: squid-evm-template@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/ethers
npm ERR!   ethers@"^5.7.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer ethers@"^6.9.0" from @subsquid/[email protected]
npm ERR! node_modules/@subsquid/evm-typegen
npm ERR!   dev @subsquid/evm-typegen@"^3.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-04-25T09_59_45_902Z-debug-0.log

@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from b536482 to de2c61e Compare March 24, 2024 16:21
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 4 times, most recently from 69395ef to f07812c Compare April 17, 2024 18:56
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from f07812c to 9eac410 Compare April 25, 2024 09:59
Copy link
Contributor Author

renovate bot commented Jun 4, 2024

⚠️ 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: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: squid-evm-template@undefined
npm WARN Found: @subsquid/[email protected]
npm WARN node_modules/@subsquid/evm-processor
npm WARN   @subsquid/evm-processor@"^1.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @subsquid/evm-processor@"^0.2.4 || ^0.3.0" from @subsquid/[email protected]
npm WARN node_modules/@subsquid/squid-gen
npm WARN   dev @subsquid/squid-gen@"^0.4.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: squid-evm-template@undefined
npm WARN Found: @subsquid/[email protected]
npm WARN node_modules/@subsquid/evm-typegen
npm WARN   peer @subsquid/evm-typegen@"^2.0.2" from @subsquid/[email protected]
npm WARN   node_modules/@subsquid/squid-gen
npm WARN     dev @subsquid/squid-gen@"^0.4.0" from the root project
npm WARN   1 more (the root project)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @subsquid/evm-typegen@"^2.0.2" from @subsquid/[email protected]
npm WARN node_modules/@subsquid/squid-gen
npm WARN   dev @subsquid/squid-gen@"^0.4.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: squid-evm-template@undefined
npm WARN Found: @subsquid/[email protected]
npm WARN node_modules/@subsquid/typeorm-codegen
npm WARN   peer @subsquid/typeorm-codegen@"^0.3.1" from @subsquid/[email protected]
npm WARN   node_modules/@subsquid/squid-gen
npm WARN     dev @subsquid/squid-gen@"^0.4.0" from the root project
npm WARN   1 more (the root project)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @subsquid/typeorm-codegen@"^0.3.1" from @subsquid/[email protected]
npm WARN node_modules/@subsquid/squid-gen
npm WARN   dev @subsquid/squid-gen@"^0.4.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: squid-evm-template@undefined
npm WARN Found: @subsquid/[email protected]
npm WARN node_modules/@subsquid/typeorm-store
npm WARN   peer @subsquid/typeorm-store@"^0.2.0" from @subsquid/[email protected]
npm WARN   node_modules/@subsquid/squid-gen
npm WARN     dev @subsquid/squid-gen@"^0.4.0" from the root project
npm WARN   1 more (the root project)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @subsquid/typeorm-store@"^0.2.0" from @subsquid/[email protected]
npm WARN node_modules/@subsquid/squid-gen
npm WARN   dev @subsquid/squid-gen@"^0.4.0" from the root project
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @subsquid/[email protected]
npm ERR! Found: @subsquid/[email protected]
npm ERR! node_modules/@subsquid/archive-registry
npm ERR!   @subsquid/archive-registry@"^3.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @subsquid/archive-registry@"^2.0.2" from @subsquid/[email protected]
npm ERR! node_modules/@subsquid/squid-gen
npm ERR!   dev @subsquid/squid-gen@"^0.4.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @subsquid/[email protected]
npm ERR! node_modules/@subsquid/archive-registry
npm ERR!   peer @subsquid/archive-registry@"^2.0.2" from @subsquid/[email protected]
npm ERR!   node_modules/@subsquid/squid-gen
npm ERR!     dev @subsquid/squid-gen@"^0.4.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-12-02T12_12_40_632Z-debug-0.log

@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 9eac410 to ac8d680 Compare June 4, 2024 15:01
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from fd443a7 to 84ab550 Compare July 2, 2024 21:20
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 84ab550 to daaab36 Compare July 21, 2024 12:25
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from daaab36 to e09f435 Compare August 6, 2024 06:13
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from e09f435 to 7741e5e Compare August 28, 2024 08:38
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 7741e5e to e132b09 Compare October 9, 2024 09:54
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from e132b09 to 939cc80 Compare December 2, 2024 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants