2 ms·

If you're getting to a semver of 145.14.7 with Semver then sack your API designer. Remember the major version bumps when it is not backward compatible. New fun

by rswail 1y ago

If you're getting to a semver of 145.14.7 with Semver then sack your API designer. Remember the major version bumps when it is not backward compatible. New functionality can be backward compatible. You can keep older semver APIs working with endpoints that support upgrading the older format to the newer internally, which allows you to enable things like sunsetting API versions to provide automated upgrade notifications. All I'm saying is that user version numbers are more a marketing exercise than anything logical.

necovek 1y ago
> then sack your API designer. Or do not use SemVer? All I am saying is that they are a communication tool regardless of the product, and there is no one single answer to which is best based on the type of software being built. You seem to want to encode good API design practices into a versioning scheme, and I claim it does not work that way ;)