CHANGELOG is behind (0.12.0 latest, but I'm running 0.13.1)
strk opened this issue · 3 comments
strk commented
Is the CHANGELOG lagging ? I'm running 0.13.1 but CHANGELOG in master branch reports latest as 0.12.0
luzpaz commented
bump...would it be possible to keep changelog up to date so it can be tracked/parsed from downstream package managers ?
For example: https://github.com/Houston4444/RaySession/releases/tag/v0.14.2 is not mentioned in Changelog
Houston4444 commented
Yes, you are right, I have to write me a release routine and apply it !
luzpaz commented
Thanks for the update!