Our current Renovate configuration pins Python dependencies to exact versions.
Since this project uses Flit and PEP 621 and declares dependencies in pyproject.toml, we should instead maintain version ranges that reflect what is actually tested and compatible.
Using rangeStrategy: replace ensures that dependency ranges are updated only when a new version is released outside the existing range and only after CI tests confirm that the project still works.
This strategy keeps the allowed range accurate, minimal, and test-verified, rather than pinned or overly broad.