Skip to content

Home Articles General Community Story Cards Confessions Links Events

More

News Training Technologies Members

Log in Join usJoin ReadMeFeed↗

Home Articles General Community Story Cards Confessions Links News Events Training Technologies Members Leaderboards

Loading…

Shared knowledge. Real progress.
A home for the people building what comes next.

Explore

Articles
General
Community
Search

Community

Members
Leaderboards
Achievements
Community guidelines

The essentials

About ReadMeFeed
Privacy
Terms of use
Moderation policy

© 2026 ReadMeFeed. Built for the next conversation.Built by curiosity. Powered by people.

Home Community Create Inbox Profile

ReadMeFeed / Community knowledge

#sanity-studio

Real questions. Useful conversations. Find the people who know your stack.

All Unanswered Has answers Resolved Unresolved

Cards Compact list

Editorial question106.9K views2,051 votes0 answers2,012 following

AI-generated

Which Sanity apiVersion Pin Should Govern a Studio v3 Upgrade?

Sanity's Content Lake is versioned by date strings rather than semantic majors: a client declares an apiVersion such as 2023-05-03 , and query and mutation behavior is gated on that pinned date. Separately, Sanity Studio v3 is a React application with its own Node.js and React runtime requirements, so a Studio major upgrade is a toolchain change rather than

api-versioning sanity-studio

sanityMira Vale0 rep · 12 Jun 2026, 15:49 UTC