API versioning strategies — URL path, header, query param, content negotiation — with breaking change classification, deprecation timelines, migration patterns, and multi-version support. Use when evolving APIs, planning breaking changes, or managing version lifecycles.
- Versioning Strategies — URL path, query param, header, content negotiation comparison
- URL Path Versioning and Header Versioning implementation examples
- Semantic Versioning for APIs (MAJOR, MINOR, PATCH)
- Breaking vs Non-Breaking Changes classification
- Deprecation Strategy — announce, sunset period, removal timeline
- Sunset HTTP Header (RFC 8594) usage
- Migration Patterns — adapter, facade, versioned controllers, API gateway routing
- Multi-Version Support architecture and principles
- Client Communication — changelogs, migration guides, SDK versioning
- Anti-Patterns and common mistakes
- Evolving APIs with breaking changes
- Planning API deprecation and sunset timelines
- Implementing multi-version API support
- Writing migration guides for API consumers
- Choosing a versioning strategy for a new API
npx add https://github.com/wpank/ai/tree/main/skills/api/api-versioningnpx clawhub@latest install api-versioningFrom your project root:
mkdir -p .cursor/skills
cp -r ~/.ai-skills/skills/api/api-versioning .cursor/skills/api-versioningmkdir -p ~/.cursor/skills
cp -r ~/.ai-skills/skills/api/api-versioning ~/.cursor/skills/api-versioningFrom your project root:
mkdir -p .claude/skills
cp -r ~/.ai-skills/skills/api/api-versioning .claude/skills/api-versioningmkdir -p ~/.claude/skills
cp -r ~/.ai-skills/skills/api/api-versioning ~/.claude/skills/api-versioningapi-design— Resource modeling, HTTP semantics, pagination, error formatsapi-development— Full API development lifecycle orchestration
Part of the API skill category.