SemVer is about the public API, it says nothing about test-coverage, internal changes or transient dependencies. The point of SemVer is to answer "if I trust t

SemVer is about the public API, it says nothing about test-coverage, internal changes or transient dependencies. The point of SemVer is to answer "if I trust the authors of this library to be as good or better than me at writing libraries, is it safe to upgrade?". The moment you don't trust the authors of the library to be as good or better than you it sorta breaks apart as a covenant, but it will still show the intent of the author. So SemVer has problems, but CalVer just shows "I tagged a release at a date". IMO badly practiced SemVer is better than perfect CalVer simply because I can open an issue of fix something that was broken because of SemVer, but with CalVer I need to live with any breakages regardless of if they were intentional or not.