Update dependency @typechain/ethers-v5 to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@typechain/ethers-v5	9.0.0 → 11.1.2

---

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

v10.2.1

Compare Source

Patch Changes

• 5b0759d: Remove obsolete peer dependency @ethersproject/bytes@^5.0.0 from target-ethers-v5
• a036651: Fix for unused type in new ethers-v5 codegen

v10.2.0

Compare Source

Minor Changes

• 31e6957: Add const assertion for exported ABI

v10.1.1

Compare Source

Patch Changes

• Updated dependencies [bbc9656]
  • typechain@​8.1.1

v10.1.0

Compare Source

Minor Changes

• 015abb2: Added support for inputs wrapped in promise for ethers-v5 target.

Patch Changes

• Updated dependencies [63691c4]
  • typechain@​8.1.0

v10.0.0

Compare Source

Depends on typechain ^8.0.0.

Major Changes

• 3a8a99a: Directory tree in generated types now reflects the directory tree in the inputs. Also, only the main contract
  type is reexported from each file.

  This change solves a number of name clashing problems. All generated code can still be imported after updating the
  import path.

• 978490f: We are not emitting contractName fields on contracts and factories anymore.

  Why?
  contractName breaks polymorphism for example: exact token implementation is not assignable to token interface.

  What do to?
  We are adding optional flag --discriminate-types to continue emitting contractName.

Minor Changes

• d86d048: The method overloads for getEvent, getFunction, decodeFunctionResult, encodeFunctionData follow these rules:

  • If these entities are not overloaded in the contract ABI and --always-generate-overloads is off, just the
    entities' names are used (without the signature)
  • If the entities are overloaded, only signatures are used to
    disambiguate them
  • If --always-generate-overloads is on, additional overloads are generated for functions that are
    not ambiguous
  • For the method and event names in the events and functions properties only signature names are used
    (that's according to the ethers API - they don't use shorthand naming).

• e447bfb: Added optional config.inputDir property and --input-dir flag to control directory structure in generated
  types. If not set, it's inferred as lowest common path of all ABI files.

• a59ae6e: Prefer import type in generated files when possible

• 47ab651: For every event, TypeChain now emits an interface with its named properties.

  Before

  export type ApprovalEvent = TypedEvent<
    [string, string, BigNumber],
    { owner: string; approved: string; tokenId: BigNumber }
  >

  After

  export interface ApprovalEventObject {
    owner: string
    approved: string
    tokenId: BigNumber
  }
  export type ApprovalEvent = TypedEvent<[string, string, BigNumber], ApprovalEventObject>

Patch Changes

• 2395289: ContractFactory subclasses now use explicit "override" modifiers.

  TypeScript version 4.3 or newer is now required.

• 975a9dc: Fix type generation for arrays of nested structs ex: GovernanceMessage.Call[][] calldata _remoteCalls.

  Fix structs parser in typechain package. Now only struct tuples are registered.

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.