Semver is one way, but yes. It annoys me when libraries "clean up" (churn) their codebase when they should've thought more carefully about designing the interf

Semver is one way, but yes. It annoys me when libraries "clean up" (churn) their codebase when they should've thought more carefully about designing the interface (the contract) before publishing it. Code churn often creates more pointless work for N library users. I swear that most code churn is to make a project look "alive" or to give people something to do / job security. Deprecate slowly and have semi-automated user code fixups and notes.