fter merging centralised CI/CD (#39), both omop-emb and its upstream dependencies bump MAJOR only via an explicit breaking label. We can drop the exact pins on omop-alchemy and oa-configurator in favour of 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.0dev extra oa-configurator[postgres]>=0.1.1 -> oa-configurator[postgres]>=0.1.2,<1.0.0 (this extra was already a floor-only range but out of sync with the main pin, align it)
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.
fter merging centralised CI/CD (#39), both omop-emb and its upstream dependencies bump MAJOR only via an explicit
breakinglabel. We can drop the exact pins onomop-alchemyandoa-configuratorin favour of 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.0devextraoa-configurator[postgres]>=0.1.1->oa-configurator[postgres]>=0.1.2,<1.0.0(this extra was already a floor-only range but out of sync with the main pin, align it)CI 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.