GraphQL commonly evolves through field and enum-value deprecation rather than creating /v2 and /v3 versions of the entire API.

A deprecated field remains available while clients migrate to its replacement. The schema can communicate the reason for the deprecation and identify the preferred alternative.

Deprecation is effective only when teams monitor usage and actively migrate clients. Leaving deprecated fields indefinitely can eventually create a confusing and difficult-to-maintain schema.