5 ms·
First: You should never trust semver anyways, not where it matters. Second: even in semver, you can bump all the way you want, especially the major version. Jus
by groestl 4y ago
First: You should never trust semver anyways, not where it matters. Second: even in semver, you can bump all the way you want, especially the major version. Just don't skip bumping when you break stuff.
- 9dev 4y agoBeing able to trust it is the entire raison d'être of semver. Everyone keeps complaining about it, but it's working splendid for hundreds of thousands of code bases.
- groestl 4y agoIt's best effort, and can make your life easier, but please treat it that way (best effort). For everything that matters, review and test even revision bumps.
- 9dev 4y agoWith third-party code, you're always relying on the best effort of others. Of course a version number doesn't relieve you of the need to run tests on your code base, but the probability for semver issues and code bugs should be about equally high - so there's no reason to trust one but not the other.
- huijzer 4y agoI think it can be okay in ecosystems where developers understand and respect semver