jargon

Backend & systems·API and interface design

you renamed the field and every client that was reading it starts getting nulls in production.

Breaking change

Any change that requires callers to change to keep working. Removals, renames, type narrowing, new required inputs and changed error semantics all qualify; so does making a previously optional field mandatory. The cost is not the change, it is the coordination: you now need every consumer to move before you can finish.

Commonly confused with