Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 2, 2024

This PR contains the following updates:

Package Change Age Confidence
@subsquid/typeorm-migration 0.1.61.3.0 age 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.

@renovate
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: ethers@5.7.2
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/evm-typegen@3.3.0
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
@renovate
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/evm-processor@0.4.0
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/squid-gen@0.4.3
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/evm-typegen@2.1.1
npm WARN node_modules/@subsquid/evm-typegen
npm WARN   peer @subsquid/evm-typegen@"^2.0.2" from @subsquid/squid-gen@0.4.3
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/squid-gen@0.4.3
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/typeorm-codegen@0.3.3
npm WARN node_modules/@subsquid/typeorm-codegen
npm WARN   peer @subsquid/typeorm-codegen@"^0.3.1" from @subsquid/squid-gen@0.4.3
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/squid-gen@0.4.3
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/typeorm-store@0.2.2
npm WARN node_modules/@subsquid/typeorm-store
npm WARN   peer @subsquid/typeorm-store@"^0.2.0" from @subsquid/squid-gen@0.4.3
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/squid-gen@0.4.3
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/squid-gen@0.4.3
npm ERR! Found: @subsquid/archive-registry@3.0.0
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/squid-gen@0.4.3
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/archive-registry@2.1.14
npm ERR! node_modules/@subsquid/archive-registry
npm ERR!   peer @subsquid/archive-registry@"^2.0.2" from @subsquid/squid-gen@0.4.3
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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-01-05T22_38_59_690Z-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
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 939cc80 to 55dcd0c Compare December 20, 2024 15:15
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from 0cfa9f3 to 5b0c25f Compare January 30, 2025 15:19
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from 5f39746 to 3ac22e6 Compare February 9, 2025 14:54
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from 8acfd46 to 3c2ae74 Compare March 6, 2025 05:13
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 3 times, most recently from 6881edc to eb242d4 Compare March 17, 2025 15:00
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from eb242d4 to 89cf803 Compare April 1, 2025 09:33
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from 850b2e7 to dfb3d7c Compare April 11, 2025 18:03
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 5 times, most recently from 547ceaf to a53403c Compare May 12, 2025 21:00
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 4 times, most recently from 7b853b0 to bed0cff Compare May 21, 2025 05:16
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 5 times, most recently from 024fd68 to 09dbb05 Compare May 31, 2025 03:34
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 09dbb05 to 653302c Compare June 22, 2025 10:59
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 653302c to 8d6537f Compare July 2, 2025 16:58
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from 0c6fe8c to 779b401 Compare August 10, 2025 15:49
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 779b401 to 37ae443 Compare August 19, 2025 12:00
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from c2cedbc to 725765c Compare September 25, 2025 17:38
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 725765c to 07e6d0d Compare October 6, 2025 15:31
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch 2 times, most recently from 0fe4784 to 7485eba Compare October 22, 2025 08:55
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 7485eba to b1984fd Compare November 10, 2025 22:54
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from b1984fd to be55afa Compare November 18, 2025 23:16
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from be55afa to 9ddec84 Compare December 3, 2025 15:03
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 9ddec84 to 969be20 Compare December 31, 2025 18:14
@renovate renovate bot force-pushed the renovate/subsquid-typeorm-migration-1.x-lockfile branch from 969be20 to d229409 Compare January 5, 2026 22:39
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.

1 participant