Skip to content

Test or narrow the supported viem version range #2

Description

@ryley-o

Problem

ABX packages declare a broad viem range beginning at ^2.21.0, but the repository does not test clean consumers at the declared boundary or across later allowed releases. An allowed version can therefore introduce type incompatibilities without CI noticing.

Desired outcome

Make the declared compatibility range an executable claim.

Acceptance criteria

  • Add clean-consumer typecheck coverage at the minimum supported version and a current allowed version, or narrow the declared range to what is actually supported.
  • Cover the public SDK types as consumed outside the workspace, not only source builds using the repository lockfile.
  • Document the supported range consistently across published packages.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency fileenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions