Post

Hi Mr Semver here (not joking) it’s fine to release a non-breaking 2.0.0. You MUST if you have breaking ones, but it says nothing about that only being acceptable when there is breakage.

Funny enough when I do revise things it’ll probably be called semver 3.0.0 and I don’t intend for it to have user-visible breaking changes but also I don’t want to argue about it

We use semver on very high merge density software (every merge is a potential release, so always increasing), so a 1.100 is nothing bizarre to us. But we usually elect a very fun, impactful and meaningful increment to call a major version update. Only use the breaking mentality for libraries