The draft model can now be switched off by setting the document.drafts.enabled configuration option to false. When the draft model is switched off, drafts will not appear in Studio, and users may only create or edit documents inside a release (unless they are live-edit documents).

export default defineConfig({
  // ...
  document: {
    drafts: {
      enabled: false
    }
  }
})

If the draft model is switched off while the dataset contains drafts, a banner will be displayed when opening the document in Studio allowing you to compare the draft content, and publish or discard the obsolete draft. This makes it possible to safely switch off the draft model without running a bulk document migration.

The draft model is switched on by default.

Vision now supports datasets config option, allowing users to configure which datasets to display in the tool

defineConfig({
    // ...,
    plugins: [
      visionTool({datasets: ['production', 'test']}),
    ]
  })

The Portable text Editor now allows you to open referenced documents from annotation popups.

List counts are now improved and should work more predictably. For example, the correct list count for numbered list items outdented to the 10th level will now display correctly.

Functions run locally now receive a context.local property set to true in both the sanity functions test and sanity functions dev commands. This allows you to run code specific to local invocations. In production, context.local is undefined. See the Functions handler reference for more context properties.

Functions will now find dependencies at the project-level, or the function-level depending on the location of your package.json manifests. If a function contains a package.json and dependencies in the individual function folder, it will use them during testing and deployment. If a function lacks local dependencies, it will use the package.json located alongside the blueprints configuration file (sanity.blueprint.ts).

You can learn more in the function dependency management guide.

On July 15th, the sanity package is moving from v3 to v4. The only breaking change is that it now requires Node.js 20, where it previously required Node.js 18. Learn more about why we're making this change and what it means for your apps.

• Fixes issue where delete changes were not being displayed correctly in Review Changes.
• Restores exports removed in 3.95.0 and adds deprecation warnings to exports related to scheduled-publishing from the sanity package.
• Fixes an issue where it was possible to create a new document version when the Content Releases feature was turned off for a studio.

To initiate a new Sanity Studio project or upgrade an existing one, please refer to our comprehensive guide on Installing and Upgrading Sanity Studio.

If you are updating from a version earlier than 3.37.0, you should also check out this article to ensure your dependencies are up to date.