Skip to content

docs: remove outdated Sanity Studio major version branding - #1930

Open
stipsan wants to merge 1 commit into
mainfrom
cursor/remove-studio-v3-refs-18af
Open

docs: remove outdated Sanity Studio major version branding#1930
stipsan wants to merge 1 commit into
mainfrom
cursor/remove-studio-v3-refs-18af

Conversation

@stipsan

@stipsan stipsan commented Aug 20, 2026

Copy link
Copy Markdown
Member

Summary

Removes consumer-facing “Sanity Studio v3” (and similar major-pinned) wording from READMEs, package descriptions, and agent guidance so docs stay version-agnostic as Studio majors advance.

Changes

  • Rewrote plugin READMEs / upgrade docs that branded the current line as “for Studio v3” or “migrating to Studio v3”
  • Softened package descriptions for sanity-plugin-media and sanity-plugin-utils
  • Made @sanity/plugin-kit ESM-only verify messaging version-agnostic
  • Updated transfer-skill changeset examples to avoid pinning Studio majors in future ports
  • Left historical CHANGELOG.md entries untouched
  • Kept intentional legacy Studio v2 notes where they disambiguate old branches

Testing

  • Grep audit: no remaining Studio v3/v5+/v6 branding outside changelogs and agent “do not say this” guidance (only intentional legacy v2 notes remain)
  • @sanity/plugin-kit verify-package Vitest suite passed (snapshot updated)
Open in Web Open in Cursor 

Reword READMEs, package descriptions, and agent guidance to be
version-agnostic so docs do not go stale when Studio majors advance.
Keep historical CHANGELOG entries and intentional legacy v2 notes.
@stipsan stipsan added the 🤖 bot label Aug 20, 2026 — with Cursor
@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
plugins-studio Ready Ready Preview Aug 20, 2026 9:51am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
plugins-e2e-test-studio Ignored Ignored Aug 20, 2026 9:51am

Request Review

@changeset-bot

changeset-bot Bot commented Aug 20, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: e0a03d9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages
Name Type
sanity-plugin-media Patch
@sanity/plugin-kit Patch
sanity-plugin-utils Patch
sanity-plugin-documents-pane Patch
sanity-plugin-workflow Patch
@sanity/document-internationalization Patch
@sanity/orderable-document-list Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions

github-actions Bot commented Aug 20, 2026

Copy link
Copy Markdown

✅ E2E Tests

🟢 26 passedview full reportview run

Studio: https://plugins-e2e-test-studio-n9frunezd.sanity.dev

Datasets: pr-1930-chromium-32355979425, pr-1930-firefox-32355979425

@github-actions

Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 32.01% 5511 / 17213
🔵 Statements 31.78% 5815 / 18294
🔵 Functions 27.79% 1428 / 5137
🔵 Branches 23.35% 2831 / 12123
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
packages/@sanity/plugin-kit/src/actions/verify/validations.ts 47.25% 47.45% 21.62% 48.48% 21-411
Generated in workflow #9312 for commit e0a03d9 by the Vitest Coverage Report Action

@stipsan
stipsan marked this pull request as ready for review August 20, 2026 10:28
@stipsan
stipsan requested a review from a team as a code owner August 20, 2026 10:28
@stipsan
stipsan requested review from a team and pedrobonamin and a lite review from Copilot and removed request for a team August 20, 2026 10:28

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes consumer-facing references to specific Sanity Studio major versions (eg “Studio v3/v5+”) across plugin READMEs, package descriptions, and plugin-kit verification messaging to keep documentation version-agnostic over time.

Changes:

  • Updated multiple plugin READMEs/docs to remove major-pinned Studio wording while keeping legacy v2 notes where helpful.
  • Adjusted npm package descriptions for sanity-plugin-media and sanity-plugin-utils.
  • Reworded @sanity/plugin-kit ESM-only verification message + docs and updated the corresponding snapshot.

Reviewed changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
plugins/sanity-plugin-workflow/README.md Removes “Studio v2” branding in a section heading/body.
plugins/sanity-plugin-utils/package.json Makes package description version-agnostic.
plugins/sanity-plugin-studio-smartling/README.md Reframes migration section away from “Studio v3” and updates related links/wording.
plugins/sanity-plugin-media/README.md Removes “for Studio v3” branding and keeps a legacy v2 branch note.
plugins/sanity-plugin-media/package.json Replaces major-pinned description with a general product description.
plugins/sanity-naive-html-serializer/README.md Renames “v2-to-v3” section to a version-agnostic “Schema access changes”.
plugins/@sanity/vercel-protection-bypass/README.md Removes Studio-major requirement line from the IMPORTANT callout.
plugins/@sanity/orderable-document-list/README.md Rewords a “Breaking change in v3” note to a version-agnostic configuration note.
plugins/@sanity/language-filter/README.md Renames “Changes in V3” heading to “Schema options”.
plugins/@sanity/document-internationalization/docs/00-upgrade-from-v1.md Makes upgrade guidance less Studio-major specific while keeping legacy v2 branch guidance.
plugins/@sanity/cross-dataset-duplicator/README.md Removes “Studio v3” from image alt text.
packages/@sanity/plugin-kit/test/snapshots/verify-package.test.ts.snap Updates snapshot for ESM-only validation message wording.
packages/@sanity/plugin-kit/src/actions/verify/validations.ts Makes ESM-only validation wording version-agnostic.
packages/@sanity/plugin-kit/README.md Updates docs wording for esmOnly guidance to remove major pinning.
CONTRIBUTING.md Rewords Studio baseline bullet to avoid naming a specific major.
.changeset/utils-description.md Patch changeset for sanity-plugin-utils description wording.
.changeset/plugin-kit-esm-message.md Patch changeset for @sanity/plugin-kit ESM verify message wording.
.changeset/media-description.md Patch changeset for sanity-plugin-media description wording.
.agents/skills/plugin-transfer/SKILL.md Updates transfer-skill guidance/examples to avoid pinning Studio majors.
Suppressed comments (1)

packages/@sanity/plugin-kit/src/actions/verify/validations.ts:221

  • The phrase “Sanity Studio, which is pure ESM” reads like it applies to all Studio versions. To avoid misleading consumers while staying version-agnostic, consider wording this as “supported Sanity Studio versions are pure ESM”.
      package.json ships CommonJS (CJS) output, but Sanity plugins target Sanity Studio, which is pure ESM.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +192 to +193
* Bans CommonJS interop in package.json. The plugin baseline is Sanity Studio,
* which is pure ESM, so there is no reason to publish a parallel CJS build anymore. This flags:
Comment on lines +473 to 474
`main`/`module` fields). This is discouraged: plugins target Sanity Studio, which is pure ESM, and
shipping a parallel CJS build can have unintended side-effects. The supported Node.js versions handle
----------------------------------------------------------
[error]
package.json ships CommonJS (CJS) output, but Sanity plugins target Sanity Studio v5+, which is pure ESM.
package.json ships CommonJS (CJS) output, but Sanity plugins target Sanity Studio, which is pure ESM.
Comment on lines 6 to +7
> [!IMPORTANT]
> This plugin requires React 19.2 or later, and Sanity Studio v4.
> This plugin requires React 19.2 or later.
Serialized files are identical for both formats (items are identified by their language code), and `BaseDocumentMerger.internationalizedArrayMerge` writes patches in whichever format the target document already uses, preserving existing item keys when replacing.

## v2-to-v3-changes
## Schema access changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants