It seems if project dropping support for previously supported environment it should be a breaking change. Since this wording - > MAJOR version when you make incompatible API changes Implies that API needs to be changed, not internal "workarounds" for such environment, can we make it more clear?