Update dependency @typechain/ethers-v5 to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typechain/ethers-v5	^10.0.0 -> ^11.0.0

---

Release Notes

ethereum-ts/Typechain (@​typechain/ethers-v5)

v11.1.2

Compare Source

Patch Changes

• Updated dependencies [3469800]
  • typechain@8.3.2

v11.1.1

Compare Source

Patch Changes

• Updated dependencies [9107713]
  • typechain@8.3.1

v11.1.0

Compare Source

Minor Changes

• c4720b9: fix tuples in event signatures and also arrays of tuples in functions

Patch Changes

• Updated dependencies [c4720b9]
  • typechain@8.3.0

v11.0.1

Compare Source

Patch Changes

• Updated dependencies [cd4bb0f]
  • typechain@8.2.1

v11.0.0

Compare Source

Major Changes

• 3eb6ed6: Removes PromiseOrValue

Minor Changes

• 15541e4: Support for nodenext style import paths with new CLI flag: --node16-modules

Patch Changes

• Updated dependencies [15541e4]
  • typechain@8.2.0

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Mend Renovate. View repository job log here.

[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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @typechain/hardhat@6.1.6
npm ERR! Found: @typechain/ethers-v5@11.1.2
npm ERR! node_modules/@typechain/ethers-v5
npm ERR!   dev @typechain/ethers-v5@"^11.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @typechain/ethers-v5@"^10.2.1" from @typechain/hardhat@6.1.6
npm ERR! node_modules/@typechain/hardhat
npm ERR!   dev @typechain/hardhat@"^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @typechain/ethers-v5@10.2.1
npm ERR! node_modules/@typechain/ethers-v5
npm ERR!   peer @typechain/ethers-v5@"^10.2.1" from @typechain/hardhat@6.1.6
npm ERR!   node_modules/@typechain/hardhat
npm ERR!     dev @typechain/hardhat@"^6.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-06T15_53_45_302Z-debug-0.log

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 11.x releases. But if you manually upgrade to 11.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.