Current situation:
- Last usable release:
0.2.0 (2019)
- Version
0.4.0 was published but introduced overly aggressive typographic apostrophe normalization
- Latest commit (after 0.4.0) reverts this problematic behavior
- Current usage: Both Geneanet and community Geneweb remain pinned to 0.2.0
Problem:
We are currently forced downstream to use git pins to avoid the 0.4.0 regression. It would be better if we can depend on a proper 0.5.0 release incorporating the fix commit.
Request:
Could you please publish version 0.5.0 with the latest commit? This would provide a stable, non-intrusive release suitable for production use (as required for Roglo support).
Same as Calendars, without proper releases, we may need to vendor the code, reducing ecosystem cohesion.
Suggested workflow:
git tag -a v0.5.0 -m "Release 0.5.0"
git push origin v0.5.0
opam publish https://github.com/geneweb/unidecode/archive/v0.5.0.tar.gz
Current situation:
0.2.0(2019)0.4.0was published but introduced overly aggressive typographic apostrophe normalizationProblem:
We are currently forced downstream to use git pins to avoid the 0.4.0 regression. It would be better if we can depend on a proper 0.5.0 release incorporating the fix commit.
Request:
Could you please publish version
0.5.0with the latest commit? This would provide a stable, non-intrusive release suitable for production use (as required for Roglo support).Same as Calendars, without proper releases, we may need to vendor the code, reducing ecosystem cohesion.
Suggested workflow:
git tag -a v0.5.0 -m "Release 0.5.0" git push origin v0.5.0 opam publish https://github.com/geneweb/unidecode/archive/v0.5.0.tar.gz