davila7--claude-code-templates/cli-tool/components/skills/development/api-patterns/versioning.md

Versioning Strategies

Plan for API evolution from day one.

Decision Factors

Strategy	Implementation	Trade-offs
URI	/v1/users	Clear, easy caching
Header	Accept-Version: 1	Cleaner URLs, harder discovery
Query	?version=1	Easy to add, messy
None	Evolve carefully	Best for internal, risky for public

Versioning Philosophy

Consider:
├── Public API? → Version in URI
├── Internal only? → May not need versioning
├── GraphQL? → Typically no versions (evolve schema)
├── tRPC? → Types enforce compatibility