Skip to content

Release 2026.2.5#777

Draft
bencap wants to merge 12 commits into
mainfrom
release-2026.2.5
Draft

Release 2026.2.5#777
bencap wants to merge 12 commits into
mainfrom
release-2026.2.5

Conversation

@bencap

@bencap bencap commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

EstelleDa and others added 12 commits May 15, 2026 11:53
…onstraintToReplacesId

Bugfix/estelle/706/unique constraint to replaces
Emit a va/{urn}.va.ndjson file per mapped score set in the public data
export, one record per current mapped variant carrying its highest
materialized VA-Spec layer.

- add variant_highest_level_annotation to resolve the highest available
  layer (pathogenicity > functional statement > study result), returning
  None for variants without a post-mapped allele
- extract get_current_mapped_variants_for_annotation as the shared
  eager-load source of truth for the annotated-variant endpoints and the
  export, and route the three streaming routers through it
- document the va/ output, layer ladder, and the functional-evidence-only
  caveat in the dump README
- cover the resolver with unit tests across the uncalibrated, functional,
  pathogenicity, and unmapped cases
- Omit the score-calibration "Baseline score" extension when no baseline
  score exists. Extension.value is required, so a null value was stripped
  by model_dump(exclude_none=True) and the object no longer re-parsed
  through the VA-Spec models. This also corrects the API's VA-Spec
  streaming endpoints, which share the builder.
- Gate dump annotation files on the presence of current mapped variants,
  so score sets whose mappings are all superseded no longer emit empty or
  stale annotation files.
- Newline-terminate every NDJSON record to match the API streams and keep
  line-based consumers happy.
- Add regression tests covering the baseline-score extension round-trip.
…-mapped-variants-in-dump

 Export mapped variants and add README for public data dump
@coveralls

coveralls commented Jun 23, 2026

Copy link
Copy Markdown

Coverage Report for CI Build 28042255045

Coverage decreased (-0.06%) to 89.135%

Details

  • Coverage decreased (-0.06%) from the base build.
  • Patch coverage: 12 uncovered changes across 2 files (26 of 38 lines covered, 68.42%).
  • No coverage regressions found.

Uncovered Changes

File Changed Covered %
src/mavedb/lib/score_sets.py 11 4 36.36%
src/mavedb/routers/score_sets.py 15 10 66.67%
Total (4 files) 38 26 68.42%

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 14285
Covered Lines: 12733
Line Coverage: 89.14%
Coverage Strength: 0.89 hits per line

💛 - Coveralls

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.

3 participants