Use tagging in repo to mark releases

[quasipedia]

Great extension, and great that is actively maintained. Every time I see an upgrade, I need to check the commit history to see what's new, and remember at what point the previous release was... released.

Using a git tag would solve that problem as - provided one uses semver - github will pick up those as releases automatically.

Bonus feature: now that the extension has a "settings" and "about" space, the release notes could be displayed there directly (you can use github API to pull those directly from the git tag comment...).

Thanks for maintaining this inspiring little extension! :)

[Elinvention]

Thank you for your support and feedback. I'm going to follow your suggestion and I just tagged version 7.

I'll also try to implement the release notes directly in the settings, although I'd like not to use github's api to download something that could be in a simple text file. Can GitHub generate such file?

[quasipedia]

Since the extension already requires the Internet to work, I would simply use the API and be done with it (eventually caching the result until an upgrade). But - should I wish to have it packaged with the extension itself - I would use some CLI magic (the actual magic to be performed - I guess - depends by the OS you are on) around the git show <your-tag-here> command during the build stage of the extension.

[RoSk0]

Hi ,

Thanks for the extension!

Familiarise yourself with https://semver.org/.

I would also recommend using of the free CI services for this task, for example Travis CI.

If you can script release creation from commit ID then you can use this article https://docs.travis-ci.com/user/deployment/releases to upload created during build phase release artefact to the GitHub.