scan-sanity-schema

To detect Sanity CMS schema drift, you validate local schema definitions against the live Sanity dataset. This process identifies missing or changed fields, ensuring schema integrity and preventing content workflow disruptions.

Sanity schema validation is the process of verifying type definitions and GROQ usage against the live cloud dataset. You need it when local schema definitions change, ensuring consuming packages maintain schema consistency during CMS assessments.

Yes, schema drift detection targets apps/cms-studio and related packages consuming Sanity data. It verifies type definitions and GROQ usage across these packages to maintain schema consistency during CMS studio assessments.

You validate Sanity type definitions and GROQ usage by running a scan against the cloud dataset. This enforces prerequisites, performs schema validation, and produces deterministic drift reports according to your environment configuration.

Missing or changed fields in your Sanity schema disrupt content workflows because local definitions diverge from the live dataset. Validating definitions against the cloud flags this drift for remediation, restoring schema integrity.