I didn't exactly intend to disagree with you, but I did get a bit combative there though, as I narrowed in a bit much when writing my response. I wanted to expa

I didn't exactly intend to disagree with you, but I did get a bit combative there though, as I narrowed in a bit much when writing my response. I wanted to expand (and work out my thoughts) on > A massive UI overhaul (but without breaking features) is almost definitely a major version bump as I think effect of UI changes tends to be underestimated. Just because v1 & v2 both have a button to frobnicate doesn't mean that they are equal. If v1 had a big large frobnicator in the main screen, and v2 buried it in a menu, you could say that no feature was broken, but the user interaction is very different. That sort of change often gets rolled into a minor/patch bump, but it does break workflows. However if every change like that bumped the major version, it would be noise. There would be no way to judge the scale of the changes from v9 to v23 vs v14 to v16. I'm not sure if the spirit of the law of SemVer applies here though. The type of change is not important, only how much has changed. Bugs can be features.