> You want to claim that version 3.2 is compatible with version 3.1 somehow, but how do you know that? I don't, not really. All I want to claim is that I to th

> You want to claim that version 3.2 is compatible with version 3.1 somehow, but how do you know that? I don't, not really. All I want to claim is that I to the best of my knowledge, the public API I've documented will not change. [1] It's up to the user of the library to decide what to do with that. Usually, that should be some manner of trust, but verify: a mostly-blind upgrade, but with automated sanity checks ran afterwards. But the other way around is more important: if I bump the major version, I want them to check my release notes, because I'm expecting it to be likely for them to need to follow some instructions there. Other than that I completely agree with this article. SemVer is a service to provide a quick tl;dr of your changelog, and the rest is up to consumers. [1] https://vincenttunru.com/semver-explained https://vincenttunru.com/semver-explained