The semantic versioning model just says how you should update your version if you break compatibility, not that you can't avoid breaking compatibility.

In fact, they suggest the opposite: "Before you completely remove the functionality in a new major release there should be at least one minor release that contains the deprecation so that users can smoothly transition to the new API."

https://semver.org/#how-should-i-handle-deprecating-function...