api-versioning-backward-compatibility

api-versioning-backward-compatibility - Skill Dossier

api-versioning-backward-compatibility

api-versioning-backward-compatibility

API migration strategies, deprecation workflows, and header/URL/content versioning. Activate on: API versioning, backward compatibility, deprecation, breaking change, API migration, v1 v2, sunset header. NOT for: schema evolution in data (use schema-evolution-manager), gateway routing (use api-gateway-reverse-proxy-expert).

Backend & Infrastructure

#api-versioning#backward-compatibility#deprecation#migration#semver

Allowed Tools

ReadWriteEditBash(npm:*npx:*)

Pairs With

api-gateway-reverse-proxy-expert

Gateway handles version-based routing

schema-evolution-manager

Data schema evolution parallels API versioning

graphql-server-architect

GraphQL has its own deprecation model via @deprecated

api-versioning-backward-compatibility preview

Share this skill

Twitter LinkedIn

⚡

Coming in Spring 2026 Beta

WinDAGs will match this skill automatically. Then ask:

"Use api-versioning-backward-compatibility to help me build..."

Request Early Access