Computing the next SemVer for dlang packages with dsemver

[Robert burner Schadek]

On Wednesday, 21 October 2020 at 17:58:53 UTC, Sönke Ludwig wrote:
> The thing is just that I don't think it is possible to find a 
> set of rules that always work. There will always be something 
> that should "obviously" be flagged as a breaking change and 
> something that is extremely annoying to be detected as such 
> (forcing a major version increment).

True, but if we can get 90% of the way there by a tool we would be
a lot better of then where we are today.
You should always be able to increment the SemVer by hand.

>
> But as some kind of warning/hint and with some kind of 
> integration into the version tagging process (maybe forcing a 
> manual version release on the registry after warnings come up) 
> it could definitely be really nice.

I'm thinking of a service that gives you a batch that shows you 
next SemVer
of the master branch, as a start.