2 ms·
So, because of a hypothetical concern that semver could unnecessarily declare a non-breaking change as breaking, they got rid of non-breaking changes altogether
by xg15 8y ago
So, because of a hypothetical concern that semver could unnecessarily declare a non-breaking change as breaking, they got rid of non-breaking changes altogether?
This seems a pretty roundabout way to tell users they don't want to be backwards compatible anymore.