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

chore(deps): update dependency @typechain/ethers-v5 to v11 #320

Merged
merged 1 commit into from
Dec 5, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 5, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@typechain/ethers-v5 ^9.0.0 -> ^11.0.0 age adoption passing confidence

Release Notes

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

v11.1.2

Compare Source

Patch Changes

v11.1.1

Compare Source

Patch Changes

v11.1.0

Compare Source

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

v11.0.1

Compare Source

Patch Changes

v11.0.0

Compare Source

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

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

v10.1.0

Compare Source

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

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: 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 renovate bot force-pushed the renovate/typechain-ethers-v5-11.x branch from b34adc4 to 1669346 Compare December 5, 2023 10:06
@montekki montekki enabled auto-merge December 5, 2023 10:06
@montekki montekki added this pull request to the merge queue Dec 5, 2023
auto-merge was automatically disabled December 5, 2023 13:26

Merge queue setting changed

@montekki montekki removed this pull request from the merge queue due to the queue being cleared Dec 5, 2023
@renovate renovate bot force-pushed the renovate/typechain-ethers-v5-11.x branch 2 times, most recently from 6d2874d to faea46b Compare December 5, 2023 13:57
@renovate renovate bot force-pushed the renovate/typechain-ethers-v5-11.x branch from faea46b to c1fa521 Compare December 5, 2023 14:28
@montekki montekki merged commit 113d98e into main Dec 5, 2023
6 checks passed
@montekki montekki deleted the renovate/typechain-ethers-v5-11.x branch December 5, 2023 15:45
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