I agree that the 'false sense of security' problem is one of the biggest issues that SemVer faces, but it can be remedied in a variety of ways. Nuget, for exam

I agree that the 'false sense of security' problem is one of the biggest issues that SemVer faces, but it can be remedied in a variety of ways. Nuget, for example, is strongly focused on SemVer, and most (recent) packages tend to follow it. It's a cultural issue more than a technical one. It's also very true that the responsibility is on the developer doing the upgrade, but the package maker should not make that job harder or more risky than it already is. Creating hard-to-distinguish variations that can have a big impact is not a good way to make upgrades easier.