After merging centralised CI/CD (#28), omop-graph and its upstream dependencies (omop-alchemy, oa-configurator, omop-emb) all bump MAJOR only via an explicit breaking label. We can replace the exact pins across all three with semver ranges.
Change in pyproject.toml:
omop-alchemy==0.8.0 -> omop-alchemy>=0.8.0,<1.0.0oa-configurator==0.1.2 -> oa-configurator>=0.1.2,<1.0.0omop-emb==1.1.1 / omop-emb[faiss-cpu]==1.1.1 / omop-emb[pgvector]==1.1.1 (3 extras) -> >=1.1.1,<2.0.0omop-alchemy[postgres] (postgres extra, previously no specifier) -> omop-alchemy[postgres]>=0.8.0,<1.0.0 (explicitness only, not a functional change; see note below)dev extra oa-configurator[postgres]>=0.1.1 -> oa-configurator[postgres]>=0.1.2,<1.0.0
CI now installs with uv sync --frozen, so it always tests exactly what's committed in uv.lock. The accompanying pre-commit hook (from cava-devops) keeps that in sync with pyproject.toml automatically going forward.
After merging centralised CI/CD (#28), omop-graph and its upstream dependencies (
omop-alchemy,oa-configurator,omop-emb) all bump MAJOR only via an explicitbreakinglabel. We can replace the exact pins across all three with semver ranges.Change in
pyproject.toml:omop-alchemy==0.8.0->omop-alchemy>=0.8.0,<1.0.0oa-configurator==0.1.2->oa-configurator>=0.1.2,<1.0.0omop-emb==1.1.1/omop-emb[faiss-cpu]==1.1.1/omop-emb[pgvector]==1.1.1(3 extras) ->>=1.1.1,<2.0.0omop-alchemy[postgres](postgres extra, previously no specifier) ->omop-alchemy[postgres]>=0.8.0,<1.0.0(explicitness only, not a functional change; see note below)devextraoa-configurator[postgres]>=0.1.1->oa-configurator[postgres]>=0.1.2,<1.0.0CI now installs with
uv sync --frozen, so it always tests exactly what's committed inuv.lock. The accompanying pre-commit hook (fromcava-devops) keeps that in sync withpyproject.tomlautomatically going forward.