Catching out-of-date schema errors in the CI - Best practices?

[maxb94]

I use this awesome tool across various projects, some of which have large teams of developers that are frequently committing and pushing code.

One issue I've encountered is ensuring that frontend code that is deployed to staging/production environments is using the live backend schema. Since developers run a local backend when running code generation, it's possible that, by the time they push their frontend code, the backend is out of date and the schema for which they generated their types has changed.

To solve this, I run graphql-codegen --errors-only against the live backend in my CI to ensure that code referencing an out of date schema is not deployed.

How do you handle this issue?