Update dependency @subsquid/cli to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@subsquid/cli (source)	2.13.0 -> 3.0.0

---

Release Notes

subsquid/squid-cli (@​subsquid/cli)

v3.0.0

Compare Source

v2.13.0

Compare Source

v2.12.0

Compare Source

v2.11.0

Compare Source

v2.10.5

Compare Source

v2.10.4

Compare Source

v2.10.3

Compare Source

v2.10.1

Compare Source

v2.10.0

Compare Source

v2.9.3

Compare Source

v2.9.2

Compare Source

v2.9.1

Compare Source

v2.9.0

Compare Source

v2.8.7

Compare Source

v2.8.6

Compare Source

v2.8.5

Compare Source

v2.8.4

Compare Source

v2.8.3

Compare Source

v2.8.2

Compare Source

v2.8.1

Compare Source

v2.8.0

Compare Source

v2.7.0

Compare Source

v2.6.1

Compare Source

v2.6.0

Compare Source

v2.5.0

Compare Source

v2.4.4

Compare Source

v2.4.3

Compare Source

v2.4.2

Compare Source

v2.4.1

Compare Source

v2.4.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]

⚠️ 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   dev @subsquid/evm-typegen@"^4.0.0" from the root project
npm WARN   1 more (@subsquid/squid-gen)
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   dev @subsquid/typeorm-codegen@"^2.0.0" from the root project
npm WARN   1 more (@subsquid/squid-gen)
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   @subsquid/typeorm-store@"^1.0.0" from the root project
npm WARN   1 more (@subsquid/squid-gen)
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-10-20T06_36_56_046Z-debug-0.log