Automate releasing process

[janhalama]

Now we do a lot of manual work with each NPM package release:

• bumping changelog version
• changelog update (including links to git repository)
• release PR review and merging into main
• creating gitlab release with correct version (which is error prone)

There is agreed architecture decision how we want to keep a changelog: https://www.notion.so/superface/1f77fa5a1e5f473495bb878a4c5d54a3?v=0f4018588dc0418fbba106531b48fef5&p=d770aba21aba4b50887b393f4266ead0

What should be automated:

• bumping changelog version
• generating changelog content from git commits, but still have the possibility to edit it afterwards
• release commit into main

[janhalama]

New release process proposal:

1. Developer working on new feature / bug fix / change updates CHANGELOG.MD either manually or using script. Changelog update is part of pull request with actual features / bug fixes / changes.
2. PR s reviewed and merged to main branch
3. Once it is appropriate (not necessarily after every merge to main) developer triggers manual release workflow with parameter patch / minor / major, depending what kind of release wants to release
4. Release workflow consists of following steps:
   • checkout, install, test, build
   • bump version according to patch / minor / major parameter
   • update changelog -> unreleased section is labeled with new version and timestamp, compare links to github are updated
   • commit changelog changes
   • create new tag
   • publish new version to NPM repository
   • push changes to git origin