Missing git tags

[alerque]

PyPi version is at 0.3.7, the latest git tag in this repo is 0.1.0. We're missing a few tags in there...

[felipesanches]

thanks for the reminder! We'll try to adopt the practice of tagging releases just like I regularly do with FontBakery. ;-D

[felipesanches]

I wonder how hard would it be to find out the correct git commits for each of our past releases. I may try doing so...

[alerque]

It shouldn't be too hard I wouldn't think if the release procedure didn't vary too much between versions. It would be nice to backfill tags ;-)

[alerque]

Just a gentle reminder, since I posted this issue there have been 14 new releases (0.3.8–0.4.5) to PyPi with no matching tags in the Git repository.

[m4rc1e]

I'll start adding release going forward and I'll try and include terse release notes as well.

This repo is in dire need of a cleanup, hopefully I can start making improvements to it over the course of this year. It was originally a dumping ground for write once and forget scripts. Since they're used daily, we should improve them.

[chrissimpkins]

If helpful, there is a very simple approach to auto GH release + PyPI push via GH Actions. You push a git tag and you are done. Requires the PyPI project owner to add their PyPI username/pw in this repo's "Secrets" config panel.

[m4rc1e]

Thanks Chris, I'll use this going forward.

[chrissimpkins]

I am happy to PR the config in if you'd like. Let me know if I can help.

[m4rc1e]

That would be great. Thanks Chris!

[chrissimpkins]

#265

[m4rc1e]

I've just pushed v0.5.0 which uses the new Github action, https://github.com/googlefonts/gftools/releases/tag/v0.5.0. Works perfectly.

[chrissimpkins]

Fantastic!

[m4rc1e]

I'll add the missing tags soonish. There's probably a scriptable way to do it.