Version lens What makes an API change major in practice? Existing consumers must change code, config, parsing, or workflow to keep working. Size of backend diff is irrelevant; consumer impact decides. Field change Additive field versus renamed field Compatibility usually favors additive transitions over direct replacement. Objection It is only a new enum value, so it cannot be breaking. Generated clients and exhaustive switches may reject unknown enum values. Your line Let's verify unknown-enum handling in each client or release a fallback first. Additive in schema can still be breaking in strict consumer code. The answer shifts from schema shape…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in