oa-configurator is still making breaking changes (e.g. AustralianCancerDataNetwork/oa-configurator#7) inside what would normally be semver-compatible version bumps. A >= constraint can silently pull in a release that breaks omop-alchemy, since nothing currently guarantees backward compatibility between minor/patch versions.
Fix
Pin oa-configurator to an exact version (==0.1.2) in pyproject.toml instead of >=.
Bump that pin deliberately, in lockstep with verifying compatibility, each time we intentionally upgrade, and not automatically via resolver-allowed ranges.
Future Work
Revisit once oa-configurator reaches 1.0 and adopts real semver guarantees; >=should become safe again at that point.
oa-configuratoris still making breaking changes (e.g. AustralianCancerDataNetwork/oa-configurator#7) inside what would normally be semver-compatible version bumps. A >= constraint can silently pull in a release that breaks omop-alchemy, since nothing currently guarantees backward compatibility between minor/patch versions.Fix
Pin
oa-configuratorto an exact version (==0.1.2) inpyproject.tomlinstead of >=.Bump that pin deliberately, in lockstep with verifying compatibility, each time we intentionally upgrade, and not automatically via resolver-allowed ranges.
Future Work
Revisit once
oa-configuratorreaches 1.0 and adopts real semver guarantees; >=should become safe again at that point.