4 ms·

cargo-semver-checks checks for breaking changes. minor and patch versions are defined to be backwards compatible and therefore not breaking. So why would it dis

cargo-semver-checks checks for breaking changes. minor and patch versions are defined to be backwards compatible and therefore not breaking. So why would it distinguish. For tooling it's very hard to detect between a feature and a bug fix so it's almost impossible to automate that series of checks

BugsJustFindMe 3y ago
> minor and patch versions are defined to be backwards compatible and therefore not breaking. So why would it distinguish. Indeed, why? And yet semver itself does, which is senseless.
- conradludgate 3y ago
  Because as a user of semver, I am not checking for breaking changes. I'm checking if I need to update because of a bug. As a user updating my software it's nice to know the gist of an update at a glance. As a piece of software looking for breaking changes, it is unnecessary to consider.
  - BugsJustFindMe 3y ago
    > Because as a user of semver, I am not checking for breaking changes. I'm checking if I need to update because of a bug. Semver doesn't help you do that. If you're on version 1.0.1 of my software, and I update to version 1.1.0 and then 1.1.1, have I fixed a bug that exists in 1.0.1? There's no way for you to know based on the version number. Knowing whether you need to update because of a bug is something you can only find out from change logs, not from version numbers.