Re:D3.js 5.0 is out
by icebraining on Friday March 23, 2018 @05:28AM
(#16656342)
The semantic versioning model just says how you should update your version if you break compatibility, not that you can't avoid breaking compatibility.
In fact, they suggest the opposite: "Before you completely remove the functionality in a new major release there should be at least one minor release that contains the deprecation so that users can smoothly transition to the new API."
https://semver.org/#how-should-i-handle-deprecating-function...
Why would they do that? To have extra work and to have to carry deprecated garbage and compatibility ports for a few releases more, instead of making a clean new version?
Those that need compatibility can stick with 4 until they're ready.