deprecation policy
Version 1 of the mdxcn API is stable under /api/v1/. Breaking changes will ship as /api/v2/, announced at least six months ahead on this page and in the OpenAPI description.
When an endpoint or field is deprecated, its responses may include Deprecation: true and Sunset: <HTTP-date> headers. After the sunset date, the route returns 410 Gone with an application/problem+json body.
The shadcn registry files under /r/ are versioned with the site. A registry item is never removed without a documented replacement in the OpenAPI changelog.
To hear about API and registry changes, watch releases on shadcn-labs/mdxcn. If you run a private integration that depends on the API, email hi@kshv.me so you get a heads-up.