API Versioning

1. The Pattern

A published API cannot be taken back. Clients you cannot see, cannot update, and cannot schedule have built on every field you ever shipped. So evolution runs on three disciplines: change additively whenever possible, version explicitly when you cannot, and retire old versions as a managed lifecycle.

The incident answers the module introduction's third question incorrectly when a team replaces order.state with order.status because the original field name is confusing