I don't think the problem is with semver. That has a very clear goal of describing MAJOR.MINOR.PATCH changes where MAJOR is a version increase when you make in

I don't think the problem is with semver. That has a very clear goal of describing MAJOR.MINOR.PATCH changes where MAJOR is a version increase when you make incompatible API changes. semver is merely describing the results of your changes. If you hate anything, it should be Angular for they decide when they are going to introduce incompatible changes.