Use semantic-release?

For Project Helix, we are using semantic release and despite the additional work you need to put in when committing (run npm run commit instead of git commit), we’ve found it worthwhile, as it gives us an automated release process

• a nice CHANGELOG.md: https://github.com/adobe/helix-shared/blob/master/CHANGELOG.md
• proper GitHub releases: https://github.com/adobe/helix-shared/releases
• clean NPM releases: https://www.npmjs.com/package/@adobe/helix-shared
• and even nice notifications for features and PRs that make it into a release: https://github.com/adobe/helix-shared/issues/123#issuecomment-503895542

[benjamind]

I’ve used semantic-release once or twice before and generally liked it. On our current project we’re using Rush which has similar functionality.

Once we start publishing actual usable versions I think this would be a good thing to adopt.

[trieloff]

We’ve been sharing the same token for all helix-* projects and I would have shared with your project, too – but getting a separate token from @filmaj is definitely better.