As you likely know you can tag old commits, too, and you can even have the correct date for them.
As this extension didn't have too much tags (does it?) I'd create a script to post-add them.
Having tags would:
show the latest and older releases on the main page
provide a way to inspect the code for a given release (and also to download it directly on GitHub)
allows to quickly check for differences between versions (useful for a bunch of things, including git bisect)
...
As I've said I volunteer to provide a script for post-adding the old ones (going by package.json and/or Changelog), but this would only be useful if new versions are tagged later on, too. What do you think?
Tagging new versions also provides a nice way to let people know about them (when subscribing to the tags) and also allows to use CD like GitHub actions to auto-publish to multiple marketplaces, if that's something that you'd like to have.
As you likely know you can tag old commits, too, and you can even have the correct date for them. As this extension didn't have too much tags (does it?) I'd create a script to post-add them.
Having tags would:
As I've said I volunteer to provide a script for post-adding the old ones (going by package.json and/or Changelog), but this would only be useful if new versions are tagged later on, too. What do you think?
Tagging new versions also provides a nice way to let people know about them (when subscribing to the tags) and also allows to use CD like GitHub actions to auto-publish to multiple marketplaces, if that's something that you'd like to have.