After 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)
Also wire up continuous verification (AustralianCancerDataNetwork/cava-devops#2): add .github/dependabot.yml and a lowest-direct CI job, so both new ranges are actually exercised together rather than just declared.
After 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)Also wire up continuous verification (AustralianCancerDataNetwork/cava-devops#2): add
.github/dependabot.ymland alowest-directCI job, so both new ranges are actually exercised together rather than just declared.