Sanity SDK versions.
The Sanity packages Versyka recognizes on npm, their latest releases, and where the breaking changes are documented. Monitoring checks connected repositories against these every day.
Packages we track
| Package | Registry | Latest | Status | Release notes |
|---|---|---|---|---|
@sanity/client | npm | 8.11.0 | Maintained | View → |
Latest versions from the public npm registry, checked and refreshed daily.
Sanity SDK questions
What is the latest version of the Sanity SDK?
As of 2026-10-26: @sanity/client 8.11.0 on npm.
Versions come from the public registries and are refreshed every day.
How do I upgrade the Sanity SDK without breaking my code?
Read the release notes for every major version between yours and the latest, update each call that changed, then run your typecheck, build and tests.
- Versyka's free upgrade check shows which Sanity packages in your package.json or requirements.txt are major versions behind, with the release notes.
- Versyka can do the upgrade for you: it finds every affected Sanity call, rewrites it, runs your own tests and opens a pull request only if they pass.
Does Versyka monitor Sanity SDKs?
Yes. Versyka recognizes @sanity/client (npm) in connected repositories and flags them every day when they fall a major version behind or are deprecated.
Behind on Sanity?
Versyka finds every affected Sanity call in your code, rewrites it, runs your tests and opens a pull request.