With babel_validation installed from GitHub (see #95 / #96), consumers (Babel, Babel Explorer) currently have to pin to a commit SHA, which is brittle and opaque.
Proposal
- Bump
version in pyproject.toml per meaningful change and create matching git tags (e.g. v0.2.0).
- Document the pin form in the README, e.g.
uv add "babel-validation @ git+https://github.com/TranslatorSRI/babel-validation@v0.2.0".
- (Later) consider publishing to PyPI once the API and the Translator-specific defaults are generalized — explicitly out of scope for now.
Benefit: downstream tools get reproducible, human-readable pins and a clear changelog boundary.
Filed as a follow-up to the library carve-out (#67).
With
babel_validationinstalled from GitHub (see #95 / #96), consumers (Babel, Babel Explorer) currently have to pin to a commit SHA, which is brittle and opaque.Proposal
versioninpyproject.tomlper meaningful change and create matching git tags (e.g.v0.2.0).uv add "babel-validation @ git+https://github.com/TranslatorSRI/babel-validation@v0.2.0".Benefit: downstream tools get reproducible, human-readable pins and a clear changelog boundary.
Filed as a follow-up to the library carve-out (#67).