Hi Maximilian,

It works great on repos that previously used semantic release — just be sure to do a release immediately before switching to Rolling Versions, so you start with a clean slate (i.e. no merged but un-released pull requests).

It works absolutely fine with projects that have no standard commit formatting. That was a huge part of the goal of creating this from scratch, rather than building on top of semantic release. I found that engineers on our team frequently made mistakes with semantic release formatting, no matter how long they’d been working on projects that used semantic release. With Rolling Versions, you create the release notes (which in turn trigger the automated release) as a separate step after submitting the pull request.

Currently Rolling Versions doesn’t attempt to infer anything from your commit messages, it’s entirely up to you to add the release notes after you create the pull request. I am thinking that in the future we could automatically “suggest” a change log, based on your commit messages, providing you follow one of the common conventions, but this would always be something you could edit by hand once the pull request has been created.

Does that sound like it would suit your use case?