api-versioning
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.
npx skills add majiayu000/claude-skill-registry --skill api-versioning-wpank-ai --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# API Versioning Patterns Evolve your API confidently. Version correctly, deprecate gracefully, migrate safely — without breaking existing consumers. ## Versioning Strategies Pick one strategy and apply it consistently across your entire API surface. | Strategy | Format | Visibility | Cacheability | Best For | |----------|--------|------------|--------------|----------| | **URL Path** | `/api/v1/users` | High | Excellent | Public APIs, third-party integrations | | **Query Param** | `/api/users?v=1` | Medium | Moderate | Simple APIs, prototyping | | **Header** | `Accept-Version: v1` | Low | Good | Internal APIs, coordinated consumers | | **Content Negotiation** | `Accept: application/vnd.api.v1+json` | Low | Good | Enterprise, strict REST compliance | ## Installation ### OpenClaw / Moltbot / Clawbot ```bash npx clawhub@latest install api-versioning ``` --- ## URL Path Versioning The most common strategy. Version lives in the URL, making it immediately visible. ```python from fastapi import FastAPI, APIRouter v1 = APIRouter(prefix="/api/v1") v2 = APIRouter(prefix="/api/v2") @v1.get("/users") async def list_users_v1(): return {"users": [...]} @v2.get("/users") async def list_users_v2(
- Versioning Strategies
- Installation
- OpenClaw / Moltbot / Clawbot
- URL Path Versioning
- Header Versioning
- Semantic Versioning for APIs
- Breaking vs Non-Breaking Changes
- Breaking — Require New Version
- Non-Breaking — Safe Under Same Version
- Deprecation Strategy
- Sunset HTTP Header (RFC 8594)
- Retired Version Response
- Migration Patterns
- Adapter Pattern
npx clawhub@latest install api-versioning
What does the api-versioning skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-versioning-wpank-ai --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.