All monitored APIs
CMS
Sanity API breaking changes, mapped to your GitHub repos
Versionly monitors the Sanity API (sanity.io) in the CMS catalog. When Sanity ships an OpenAPI or changelog change, we find call sites in the repositories you connect and open a reviewable auto-fix pull request.
What breaks without monitoring
- Sanity request or response fields can rename without a compile error
- CMS SDK method signatures drift between Sanity releases
- Calls to sanity.io can change auth, versioning, or payload shape
How Versionly helps
- Catalog monitoring for Sanity (sanity.io)
- Import and host detection for Sanity usage in connected repos
- File-level impact mapping and reviewable GitHub pull requests
Sanity + Versionly — FAQ
- Does Versionly auto-merge Sanity upgrades?
- No. Versionly opens a pull request when Sanity API changes hit your connected repos. Your team reviews and merges.
- How does Versionly detect Sanity usage?
- The catalog entry for Sanity matches SDK imports, package names, and typical sanity.io hosts in the repositories you choose to connect.
Next step
Connect one repo. Review the first pull request.
Start with the project that talks to payments or an LLM vendor. If the PR looks wrong, close it. Versionly does not merge.