315 B
315 B
API Versioning
- Use an explicit major API version.
- Prefer additive fields and events.
- Clients must tolerate unknown fields and events.
- Breaking changes require a new major version, fixtures, migration notes, and coordinated releases.
- Each release records minimum compatible client and server versions.