If the change actually breaks existing use, then bumping the major version of every such release is *exactly* the purpose of SemVer. One important note that is

If the change actually breaks existing use, then bumping the major version of every such release is *exactly* the purpose of SemVer. One important note that is often overlooked, as it isn't part of the short SemVer summary, is that major version 0 is special. The rules for minor and patch versions do not apply, and anything can change at any time. In other words, a project and library can explore its API freely and make as many wild changes as it pleases. Once it matures, it can be made 1.0.0, and the whole point of doing so is to communicate that the rules of major, minor and patch version bumps can be expected to be followed.