Consider semantic-release #499
Description
This will probably morph into an RFC, but just wanted to put up an issue to discuss for now. If we agree this is something worth doing I'd be happy to flesh out an actual RFC with someone.
In order to streamline some of the overhead around merging, tagging and releasing new versions of kyt, we could look into using something like semantic-release. This enables an automated pipeline where when a PR is merged to master, a CI job (via semantic-release) will generate a changelog, bump the version number according to semver commit messages (which is enforced programmatically) and then publish a new version of kyt to npm via some next or unstable tag or whatever. We can still enforce a manual "official" release against latest tag which gives us an opportunity to create messaging, upgrade guides etc for releases of interest.
Bug or Feature?
Feature
Current Behavior
Manual releases, changelogs, etc.
Desired Behavior
Automated next tag releases.