Skip to content

Upgrade to hgvs 2.0.0a0 #579

Closed
Closed

Description

@korikuzma

The latest release of hgvs (which was 3 years since the last release) is causing CI tests to fail in #578 . I haven't really looked at these in detail, but we should resolve the tests and/or update code to reflect these changes.

Activity

  1. added
    buildChanges that affect the build system or dependencies
    on Aug 15, 2025
  2. added a commit that references this issue on Aug 15, 2025
  3. changed the title [-]Upgrade to hgvs 1.5.5[/-] [+]Upgrade to hgvs 2.0.0a0[/+] on Sep 11, 2025
  4. korikuzma commented on Sep 11, 2025

    @korikuzma
    ContributorAuthor
  5. korikuzma commented on Apr 6, 2026

    @korikuzma
    ContributorAuthor

    I'm assuming this one will not result in a breaking change, but I would like to see it prioritized to get in by the time we make a v3 release.

  6. self-assigned this
    on Apr 17, 2026
  7. added
    v3Issues targeting a v3.x.x release of vrs-python
    on Apr 22, 2026
  8. theferrit32 commented on Oct 19, 2026

    @theferrit32
    Contributor

    This is completed in the v3 branch. Given that the tag and upcoming vrs-python version will be v3... we should merge vrs/2.1 into v3 and close vrs/2.1

  9. korikuzma commented on Oct 19, 2026

    @korikuzma
    ContributorAuthor

    @theferrit32 did this in #632

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

Metadata

Metadata

Assignees

Labels

buildChanges that affect the build system or dependenciesv3Issues targeting a v3.x.x release of vrs-python

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions