gql-breaking-changes

To detect GraphQL breaking changes, build your project and start the local server so the diff script can compare the local schema against the public evitaDB demo schema, generating both a diff file and a prose summary.

A breaking change in a GraphQL schema diff includes modifications that break compatibility for downstream clients, such as removing fields or changing types, which are identified by running graphql-inspector to compare schema versions.

Yes, you can check evitaDB API compatibility by running the schema diff workflow which evaluates compatibility against downstream TypeScript clients that auto-generate a GraphQL client, producing a detailed impact summary.

Run the GraphQL schema diff by executing the tools/diff-graphql-schemas.sh script after building the project and booting the local server, which uses graphql-inspector to compare schemas and output a diff file.

No, the GraphQL breaking changes analysis maintains a read-only workflow that produces a diff file and a prose summary of client-facing implications without making any code modifications to the evitaDB tree.