Consider automated releases or at the least: Conventional Commits Beta

[ghost]

While looking into pros/cons of going through Windows store for windows releases, came across:
semantic-release
which uses:
conventionalcommits

Perhaps at the moment, while in 'sponsor-support' mode there is less need for automated releases, but if that changed, the idea of this being handled somewhat by considering commit 'types' and doc, changelog, checksum and publishing might be worthwhile. The documentation for it certainly seems comprehensive at least - I think just for this it's worth a look, as many CI blends seem to be covered.

At the moment, we use package.json with electron-builder to indicate various build types and with CI config, this determines when to test, build and release (to draft or publish). Checksums are also handled.
The only part really that isn't handled is the changelog and comms to users.

At the very least, I do like the look of the Beta of: conventionalcommits - takes little effort to start using this in commits.

[ghost]

Tagging with minimal just to start following convention for commits.
Assessment tag for considering the semantic github library at some point.
Windows tag as if go down the Windows Store release, this library may be useful.

[ghost]

Just changing types of commit messages to line up with Windows store publishing might be all that we need here for now.