Currently for a release, the extension is built locally, and then attached to a release (which creates a tag).

It would be nice to automate this with a workflow that can be manually triggered, which builds the extension (if everything passes), and then create the tag + release automatically (this would also mean we get tags/release for pre-releases, which currently are more ad-hoc and not tagged).

This would avoid an error today, where I built a pre-release without first pulling master from GitHub, so it was missing the last merged PR.

(automating publishing to the store is something else to consider, but out of scope for this issue, and would involve having publish keys on GH that would need to be kept secure)