Changelog

Versioning policy

• The API is versioned in the path: /v1/
• Within a version, changes are backward-compatible only: new fields, new enum values, new endpoints
• Breaking changes ship under a new version path with a deprecation window for the old one
• Treat unknown enum values and new fields gracefully: they are not breaking

Deprecation process

1. The field/endpoint is marked deprecated in the changelog and docs
2. A Sunset header appears on responses for the deprecated surface
3. After the announced window, it is removed under the next version

Recent changes