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.0dev extra oa-configurator[postgres]>=0.1.1 → oa-configurator[postgres]>=0.1.2,<1.0.0
Also wire up continuous verification (AustralianCancerDataNetwork/cava-devops#2): add .github/dependabot.yml and a lowest-direct CI job, so all three new ranges are actually exercised together rather than just declared.
Out of scope for this issue: the postgres extra's omop-alchemy[postgres] has no version constraint at all — separate follow-up if we want to add one.
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.0devextraoa-configurator[postgres]>=0.1.1→oa-configurator[postgres]>=0.1.2,<1.0.0Also wire up continuous verification (AustralianCancerDataNetwork/cava-devops#2): add
.github/dependabot.ymland alowest-directCI job, so all three new ranges are actually exercised together rather than just declared.Out of scope for this issue: the
postgresextra'somop-alchemy[postgres]has no version constraint at all — separate follow-up if we want to add one.