Recall semantic-versioning signals and common compatibility traps.
"The field was deprecated, so removing it can be minor." A public response field is removed from a package API. Your line "Deprecation warns consumers; removal still breaks consumers and needs a major release." Deprecation lowers surprise but does not make incompatible change compatible. The response separates warning from compatibility. Objection Additive or breaking? Compatibility is about whether existing consumers can continue unchanged. Compare Patch version means what kind of change? Backward-compatible bug fixes. If consumers need to change code, it is not merely patch. Recall Major version means what kind of change? An incompatible API change that consumers must…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in