How does GraphQL versioning work? Why is there no 'v1/v2'?

GraphQL strongly discourages API versioning, advocating instead for continuous schema evolution.

In REST, breaking changes necessitate a /v2 endpoint. In GraphQL, you simply add new fields and types, and use the @deprecated directive to mark old fields as obsolete. Because clients request exact fields, adding new fields never breaks existing clients. Tools track field usage to safely remove deprecated fields once usage hits zero.