3 ms·
If their own public API hasn't changed, why would semver require that?
by eterm 4y ago
If their own public API hasn't changed, why would semver require that?
- rk06 4y agoBecause major dependecy change can break downstream users. Major does not signify that you are delivering big features, it signifies you can break existing apps. For eg: Consider CRA dependency upgrade from webpack v4 to v5. That change broke a lot of apps due to node not being polyfilled. If CRA did the change in minor version, then it would have result in breaking changes for many apps and would completely undermine semantic versioning