Migrate @sanity/personalization-plugin into the monorepo

[stipsan]

Migrate @sanity/personalization-plugin

Transfers @sanity/personalization-plugin into the monorepo using the copy plugin generator (git subtree with full history preserved).

Demo

Field-level experiment flow verified in the test studio (kitchen-sink workspace): default value, beaker "Add experiment" action, experiment selection, and variant value entry.

personalization_plugin_experiment_demo.mp4

Configured experiment with two variants

What's included

• Plugin workspace at plugins/@sanity/personalization-plugin with monorepo config (package.json, package.config.ts, tsconfig.json, tsconfig.build.json, vitest.config.ts)
• All three entry points preserved: ., ./launchDarkly, and ./growthbook (ESM-only)
• @sanity/studio-secrets dependency now resolved via workspace:* (it lives in this monorepo)
• Source adapted to monorepo lint rules (type-only imports, @sanity/ui space → gap, deprecated FormEvent → ChangeEvent, no accumulating spreads, index-signature access); targeted .oxlintrc.json override added for remaining legacy patterns (unsafe type assertions, pagination awaits-in-loop, set-state-in-effect) following the sanity-naive-html-serializer precedent
• README assets (overview.gif, beaker.svg, screenshots) and the growthbook.md / launchdarkly.md docs restored from the original repo
• Test-studio example (dev/test-studio/src/personalization) wired into the kitchen-sink workspace with a personalizationTest document using experimentString / experimentText fields
• Package exports test with snapshot covering all three entry points
• Major changeset + root README plugins table entry

Transfer verification

• Trusted publishing configured: npm trust github @sanity/personalization-plugin --file=release.yml --repository=sanity-io/plugins
• package.json dependencies/peerDependencies/exports verified against original repo
• Test studio example wired and manually verified (pnpm dev)
• pnpm format, pnpm knip, pnpm lint, pnpm build, pnpm test run all pass
• Major changeset added with validated breaking changes

Maintainer follow-up

Agents cannot complete these steps themselves. Ask the maintainer to handle them:

• Update the original repo README (https://github.com/sanity-io/sanity-plugin-personalization/blob/main/README.md) and replace it with: # [This plugin has moved](https://github.com/sanity-io/plugins/tree/main/plugins/@sanity/personalization-plugin)
• Transfer pending issues from the original repo to this monorepo and label them as personalization-plugin
• Archive the original repo: https://github.com/sanity-io/sanity-plugin-personalization/settings

_{To show artifacts inline, enable in settings.}

  

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
plugins-studio	Ready	Preview, Comment	Jun 12, 2026 2:53pm

[changeset-bot]

🦋 Changeset detected

Latest commit: 0c663d0

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

This PR includes changesets to release 1 package

Name	Type
@sanity/personalization-plugin	Major

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​react-icons@​5.6.0
	npm/​@​sanity/​assist@​6.1.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm react-icons is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: plugins/@sanity/personalization-plugin/package.json → npm/react-icons@5.6.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-icons@5.6.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report