Skip to content

merge: migrate vrs/2.1 into v3 - #674

Open
korikuzma wants to merge 23 commits into
v3from
vrs/2.1
Open

korikuzma wants to merge 23 commits into
v3from
vrs/2.1

Conversation

@korikuzma

Copy link
Copy Markdown
Contributor

close #672

korikuzma and others added 21 commits February 24, 2026 08:29
* This is from over 4 years ago and I don't think we actually need this.
There are times when we want to create releases off other branches (and
its easy to forget to update). I think we should just remove

Cherry-picked b573565
the root cause of biocommons/anyvar#467

If you have a valid variant expression, you can attach some extra kwargs
like "assembly_name" to help ground certain kinds of translation.
However, if you happen to have an invalid expression, the translator
will attempt each different format of translation, including
`_from_vrs`. If you have attached kwargs, `_from_vrs` will raise an
unexpected TypeError because it, unlike the other `_from_` methods,
doesn't include kwargs in its type signature. I can't think of a reason
why this might be the case. I also added a test to show this.
close #638

* Unsupported `fmt` in `translate_to` should raise `NotImplementedError`
close #638

* Unsupported `fmt` in `translate_to` should raise `NotImplementedError`
Pull in patches from 2.3.x branch
close #649, #466

* add `schema_id` and `maturity` class methods to core and vrs models
* include `$id`, `maturity`, and `ga4gh` metadata in `model_json_schema`
## Changes

* update models vrs 2.1.1-ballot.2026-09.1 and gkm-core
1.3.0-ballot.2026-09.1
  * Added `_abstract` classvar  
  * GKS -> GKM (deprecating classes that start with GKS)
  * Adds missing `RelativeAllele` to Variation root  

## Schema changes

_note: Use /json rather than *-source.yaml_

* Core changes:
https://github.com/ga4gh/gkm-core/compare/1.2.0..1.3.0-ballot.2026-09.1
* VRS changes:
https://github.com/ga4gh/vrs/compare/2.1.0..2.1.1-ballot.2026-09.1

---------

Co-authored-by: Larry Babb <lbabb@broadinstitute.org>
_abstract is metadata for MSP (to allow additional properties)
* GKM-Core version 1.3.0
* Also fixes constraints for `ConceptSet.concepts`
`is_intronic` only recognized introns on coding (c.) coordinates because
it gated on the interval being a `BaseOffsetInterval`. RNA (r.)
coordinates parse to a plain `Interval` whose endpoints are still
`BaseOffsetPosition`, so intronic r. variants slipped past the "Intronic
HGVS variants are not supported" guard

inspect the interval endpoints instead of the interval type. g./p.
coordinates have no base-offset positions and stay non-intronic

closes #628

---------

Co-authored-by: Kyle Ferriter <kferrite@broadinstitute.org>
Forward-merge main into vrs/2.1 so it is no longer behind. Net change to
vrs/2.1 is #642 (is_intronic r. fix); the other main commits since the merge
base (#635, #639, #645, #648) were already ported as parallel PRs.

Conflict resolution:
- src/ga4gh/core/models.py: conflict between #645 (main) and vrs/2.1's
  restructured models (#644 + gkm-core updates). Took vrs/2.1's version, which
  already includes the int Extension.value fix.
- src/ga4gh/core/__init__.py: auto-merged without conflict but incorrectly,
  duplicating main's __version__ block (undefined `version`) and
  CORE_VERSION = "1.0.0" from #648. Took vrs/2.1's version (CORE_VERSION from
  ga4gh.core.version, 1.3.0).
@korikuzma korikuzma self-assigned this Oct 19, 2026
@korikuzma

Copy link
Copy Markdown
Contributor Author

Will do a merge commit for this

@korikuzma
korikuzma marked this pull request as ready for review October 19, 2026 18:28
@korikuzma
korikuzma requested review from a team as code owners October 19, 2026 18:28

This branch has not been deployed

No deployments
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.

4 participants