Skip to main content

Versioning

GraphQL schemas will typically evolve over time. Schema designers need a strategy to ensure clients can adjust to these changes.

The traditional advice is to design your schema in a "versionless" way, deprecating but continuing to support old fields as you add replacement functionality. This means that ancient clients can continue to use a GraphQL endpoint indefinitely, but does require a significant level of foresight at schema development time. Some teams prefer a more traditional approach where GraphQL endpoints are explicitly versioned and have their own lifecycle and sunsetting timelines.