Automate release process

[emiliosheinz]

I was wondering if it wouldn't be good if we automate the release process (generate tags, releases, changelogs and publish to npm).

For example, the latest release published to npm has no release or tag in GitHub.

After some research I've found that the most used libraries for this kind of use case are:

• Google Release Please: Maintained by Google it keeps an opened pull request that you can merge when you want to release a new version. It seems to work well with a simple branch structure like the one that we have here.
• Semantic Release: I've been using this one on a personal project and it seems pretty flexible. The main pro that I can see is that it keeps track of your changelog and version always based on your latest release on GitHub and not based on some local files.
• Auto: It is used by Storybook in their Addon Kit template, it seems to be a good fit for our use case.

All the options above would require the usage of Conventional Commits.

What do you think about it?

[TomFreudenberg]

For sure a good idea in general.

I just forgot to set the tag last time - my apologies.

It's done by now.

I will look into your suggestions and come back 👍🏻

And it's on the project map as well ;-)

[TomFreudenberg]

Do you have also any suggestions from your side about automated changelogs?

[emiliosheinz]

All the libraries that I mentioned above take care of everything but in a different way. Basically, they generate the changelogs based on the commits (that's why we would need to use conventional commits), bump the package version, generate a new tag, generate a new GitHub release, and publish it to npm.