It's tough to remember that the "sem" in "semver" stands for "semantic" and implies "meaningful to other software developers". I understand why we like to try t

It's tough to remember that the "sem" in "semver" stands for "semantic" and implies "meaningful to other software developers". I understand why we like to try to automate it, but aspects of it were intentional rejections of automated version numbers in the first place and it feels like a cycle of automating things, finding failures in them when automated, and trying to remind ourselves why we shouldn't just automate every aspect of our jobs. Sometimes you need the "semantics", the human judgment calls.