> Sometimes only the patch version of the library is different so it shouldn't be breaking anything... but it does! OT: Semantic versioning’s major flaw is tha

> Sometimes only the patch version of the library is different so it shouldn't be breaking anything... but it does! OT: Semantic versioning’s major flaw is that is the presumption that the entire chain of package maintainers is extremely diligent about correctly bumping their version numbers. There have certainly been a few projects that are very good about this, but the vast majority are not. The only solution to this that I know of is to test: Manually exercise the features with the dependencies, write automated tests that check your critical needs from a dependency, or identify and run the tests from the dependency’s test suite that cover your use cases. (Also: Contribute tests that you want in the suite!)