Breaking Change
A change can break the supported contract or expose an unsupported assumption. Check both, including changes that silently alter results.
-
-
API Contracts, Compatibility, and Retirement
API changes need both a clear compatibility contract and evidence of consumer impact. Errors, retry safety, and retirement are part of that work.
-
Semantic Versioning
MAJOR.MINOR.PATCH tells users whether an upgrade can break them — but only if what counts as the public interface was declared first. That applies to data, too.
-
Data Model Change and Compatibility
The dangerous model change is the one that passes every check. See what breaks consumers, why meaning changes are invisible, and how to publish one safely.