> I disagree with the idea that sticking with a specific version of a dependency is a good solution, it creates more problems than it solves Semver addresses t

> I disagree with the idea that sticking with a specific version of a dependency is a good solution, it creates more problems than it solves Semver addresses this. You stick with a specific major version (or minor version for a 0.x release, where "minor" version changes can in fact introduce major breaks), and your dependency tool enforces this. However, it does still warn you if a newer version is available, so that you can start depending on it. (Of course, switching to a newer release is easier said than done if other modules might still depend on the previous one, and your build tool doesn't support the concurrent use of both in the same build!) This is essentially a solved problem.