Api Versioning Policy

samber/developer-platform-skills/skills/api-versioning-policy

作者 samber594cf70d343eMIT3 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫10 天前更新

Define the versioning and deprecation policy for an API - version scheme choice (URI path, header, date-based account-pinned, or deliberate no-versioning), a written breaking-change definition, deprecation notice windows by audience, sunset communication (RFC 9745 Deprecation and RFC 8594 Sunset headers), enforcement at the sunset date (fall-forward vs hard cutoff), and breaking-change governance, with REST version-and-sunset and GraphQL continuous schema evolution treated as separate policies. Use whenever the user mentions API versioning, /v2, breaking changes, deprecation, sunset dates, or migration windows - even if they never say "versioning policy". Client SDK versioning is plain SemVer and belongs to samber/developer-platform-skills@sdk-portfolio-strategy.

  1. 594cf70d343e目前提交 594cf70發布於 2026年10月8日

來源與署名

來源:samber/developer-platform-skills位於skills/api-versioning-policy提交594cf70

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架