Q44: How can schema breaking changes be caught in CI/CD pipelines?
Tools like GraphQL Inspector or Apollo Rover/Studio compare proposed SDL files against production schemas during CI builds. They detect breaking changes (e.g., removing a field, changing a non-nullable type) and fail pull requests before deployment.
Key Takeaways
- Automated CI schema checks block breaking changes prior to production releases.
Knowledge Check
Which of the following field alterations constitutes a breaking change?