Skip to content

docs: add error and schema management guides#4516

Open
sarahxsanders wants to merge 2 commits into
graphql:16.x.xfrom
sarahxsanders:errors-schemaevolution
Open

docs: add error and schema management guides#4516
sarahxsanders wants to merge 2 commits into
graphql:16.x.xfrom
sarahxsanders:errors-schemaevolution

Conversation

@sarahxsanders

Copy link
Copy Markdown
Contributor

Adds last TWO guides for the GraphQL production guide improvements:

  • guide 1 is on error handling and debugging + includes format errors, custom error types, debugging production issues, and error recovery
  • guide 2 is on schema management + covers schema evolution and governance w/ versioning safely, detecting breaking changes, deprecation workflows, governance processes, and other considerations

@sarahxsanders
sarahxsanders requested a review from a team as a code owner December 7, 2025 19:16
@vercel

vercel Bot commented Dec 7, 2025

Copy link
Copy Markdown

@sarahxsanders is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel.

A member of the Team first needs to authorize it.

Comment thread website/pages/docs/production-schema-management.mdx
Rebuilt cleanly on 16.x.x; adds production-errors-debug and
production-schema-management guides, nav entries in Production &
Scaling, and cspell words.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sarahxsanders
sarahxsanders force-pushed the errors-schemaevolution branch from 9e34fa1 to 93de8e9 Compare July 16, 2026 22:43
@sarahxsanders
sarahxsanders changed the base branch from production-guides to 16.x.x July 16, 2026 22:44
Addresses review feedback: point readers at the schema-diffing utilities
GraphQL.js already ships before hand-rolling comparison. Notes the v17
consolidation into findSchemaChanges.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sarahxsanders
sarahxsanders requested a review from yaacovCR July 16, 2026 23:11
@vercel

vercel Bot commented Jul 16, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants