After merging centralised CI/CD (#28), OMOP_Alchemy's own releases are now driven by PR labels (breaking/feature/fix/dependencies), and our upstream packages follow the same convention. We can replace the exact pins on oa-configurator and orm-loader with semver ranges so compatible upstream releases flow through without a manual bump each time.
Change in pyproject.toml:
oa-configurator==0.1.2 → oa-configurator>=0.1.2,<1.0.0orm-loader==0.5.1 → orm-loader>=0.5.2,<1.0.0 (orm-loader's latest published tag is already 0.5.2)oa-configurator[dev,postgres]==0.1.2 (dev extra) → oa-configurator[dev,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 both new ranges are actually exercised together rather than just declared.
After merging centralised CI/CD (#28), OMOP_Alchemy's own releases are now driven by PR labels (
breaking/feature/fix/dependencies), and our upstream packages follow the same convention. We can replace the exact pins onoa-configuratorandorm-loaderwith semver ranges so compatible upstream releases flow through without a manual bump each time.Change in
pyproject.toml:oa-configurator==0.1.2→oa-configurator>=0.1.2,<1.0.0orm-loader==0.5.1→orm-loader>=0.5.2,<1.0.0(orm-loader's latest published tag is already0.5.2)oa-configurator[dev,postgres]==0.1.2(dev extra) →oa-configurator[dev,postgres]>=0.1.2,<1.0.0Also 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.