Now that #21 landed centralised CI/CD (label-gate + release-drafter), oa-configurator only bumps MAJOR on a breaking-labelled PR. We can stop exact-pinning it and instead allow any compatible MINOR/PATCH release through automatically.
Change in pyproject.toml:
oa-configurator==0.1.2 → oa-configurator>=0.1.2,<1.0.0oa-configurator[postgres]==0.1.2 (dev extra) → oa-configurator[postgres]>=0.1.2,<1.0.0
Also wire up continuous verification (see AustralianCancerDataNetwork/cava-devops#2): add .github/dependabot.yml and a lowest-direct CI job, so the range is actually exercised rather than just declared.
Now that #21 landed centralised CI/CD (label-gate + release-drafter),
oa-configuratoronly bumps MAJOR on abreaking-labelled PR. We can stop exact-pinning it and instead allow any compatible MINOR/PATCH release through automatically.Change in
pyproject.toml:oa-configurator==0.1.2→oa-configurator>=0.1.2,<1.0.0oa-configurator[postgres]==0.1.2(dev extra) →oa-configurator[postgres]>=0.1.2,<1.0.0Also wire up continuous verification (see AustralianCancerDataNetwork/cava-devops#2): add
.github/dependabot.ymland alowest-directCI job, so the range is actually exercised rather than just declared.