I think there needs to be a much tighter definition of what the API is and not just the entire surface area. So if a project does a major update of one of its

I think there needs to be a much tighter definition of what the API is and not just the entire surface area. So if a project does a major update of one of its deps, without changing its own API, or deprecates support for an old language version or distro, it should be able to ship those in a minor version. That means that consumers who aren't keeping up with the times may be cut off in a minor update and have to do work to consume the next update. There needs to be less of an expectation that "it isn't a major update, so I won't have to lift a fucking finger and its your fault if I need to" which is what SemVer has socially turned into.