---
title: "2026-08-28 vxData domain representation upgrades"
description: "Regenerated the HistoDomainRep v2 Alembic migration, merged main, and aligned vxData package versions."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-08-28 vxData domain representation upgrades

## Work Done

- Updated mono PR #350 (`paulhager/histo-domain-rep-v2`).
- Merged current `origin/main` into the branch without conflicts.
- Replaced the hand-written HistoDomainRep v2 migration with a real `alembic revision --autogenerate` revision generated against PostgreSQL at revision `9a2a50fe3707`.
- Bumped `vxdata-schemas`, `vxdata-sdk`, and `vxdata-api` together from `3.1.0` to `3.2.0` for the additive schema/API feature.
- Validated migration upgrade, schema drift check, downgrade, and re-upgrade on a fresh PostgreSQL database.
- Ran schemas, SDK, and API lint/typecheck/tests plus the monorepo boundary check. Pushed commit `38e0425a` to the PR branch.
- Reviewed the complete PR and submitted a changes-requested review. The Alembic migration is sound, but `TISSUE_GLEASON_CELL` currently validates without its four v2 output/model references, contradicting the bundle's completeness-marker contract. Also noted that older 3.1 response models reject the new Literal values, so the rollout must upgrade consumers first even though a minor bump matches repository precedent.

## Lessons Learned: Pitfalls

- The branch already contained an older merge from `main`, but was still 21 commits behind current `origin/main`; always fetch before judging merge state.
- Ruff in `apps/vxdata-api` is configured with `include = ["src"]`, so its project-wide format/lint task reports no migration files. Alembic's generated migration formatting therefore stays as generated.
- Unrelated untracked files were present in the primary checkout. All staging had to use explicit paths.

## Lessons Learned: Improvements

- Document a short migration regeneration recipe that creates an isolated temporary PostgreSQL database, upgrades it to the migration's parent revision, then runs `alembic revision --autogenerate`.
- Add a reusable migration validation task that performs upgrade, `alembic check`, downgrade, and re-upgrade against ephemeral PostgreSQL.

Source: https://docs.virdx.dev/knowledge/inbox/2026-08-28-infrastructure-vxdata-domainrep-upgrades/index.mdx