shared-resources VS graphql-inspector

Doing this was pretty simple. You can find the repo here which is used as the master repository to push all the labels downstream and we still retain the repo specific labels in their own repository (like this)

merge-graphql-schemas will be added to the existing Schema management tools already created by The Guild (GraphQL-Toolkit, GraphQL Modules, GraphQL Inspector and graphql-code-generator)

GraphQL CLI 4.1 has been updated to use the latest versions of GraphQL Code Generator and GraphQL Inspector, which are included as recommended, best practice workflows for developing production-ready GraphQL applications.

It's an entirely open-sourced and community driven tool to help you improve and maintain your GraphQL stack. It comes with a CLI, GitHub Application and GitHub Action. You can read more on our website.

GraphQL Inspector

The new version of GraphQL Inspector comes with schema change notifications. We had it in plans for almost a year now and we're very excited to finally roll it out!

First, we are aiming for a new schema registry package. We plan on using GraphQL Inspector to check for breaking changes on individual services and the schema gateway as a whole. And thanks to GraphQL Mesh, that process will work for any type of service schema, not just GraphQL!

If you want to validate your schema as and when you push to Version control to maintain sanity, setup something like GraphQL Inspector locally and in your CI/CD pipelines to maintain your sanity. If you use the Apollo ecosystem, it comes inbuilt in the Apollo Studio or the CLI tools which it gives you.