It's the old way of versioning things, somewhat formalized.
With semver you live in this world where you are promised the versions to follow semantics, but human nature creeps in and we introduce breaking changes (like bugs!) without setting the version correctly.
With pragmatic versioning you give expectations but also convey that to upgrade you need to test that your software still works.
With semver you live in this world where you are promised the versions to follow semantics, but human nature creeps in and we introduce breaking changes (like bugs!) without setting the version correctly.
With pragmatic versioning you give expectations but also convey that to upgrade you need to test that your software still works.