Using x.y.z version numbers does not imply semver. I agree that semver as defined only really makes sense for libraries. When working on internal code, “breaki

Using x.y.z version numbers does not imply semver. I agree that semver as defined only really makes sense for libraries. When working on internal code, “breaking changes” are rarely a concern. We instead use it to mean <major overhaul>.<feature change>.<minor bugfix>. That works well as semver-ish, and is more useful than just a date or a commit hash.