Fix TypeGen workflow failure by pinning @sanity/vanilla-extract-vite-plugin to 0.1.1

[Copilot]

The TypeGen workflow started failing in the run job during pnpm typegen, specifically at schema extraction with Error: module is not defined. The regression aligns with the dependency bump that moved @sanity/vanilla-extract-vite-plugin from ^0.1.1 to ^0.2.0.

• Root cause containment

  • Reverted the catalog version of @sanity/vanilla-extract-vite-plugin in pnpm-workspace.yaml from ^0.2.0 back to ^0.1.1.

• Dependency graph update

  • Regenerated pnpm-lock.yaml to resolve @sanity/vanilla-extract-vite-plugin to 0.1.1 across affected importers and snapshots.

• Scope

  • No source code changes in plugins or tooling logic; this PR is dependency-resolution-only to restore TypeGen stability.

# pnpm-workspace.yaml
catalog:
  '@sanity/vanilla-extract-vite-plugin': ^0.1.1

---

Note

Low Risk
Dependency pin and lockfile-only change to fix CI TypeGen; main tradeoff is staying on an older Vite vanilla-extract plugin until 0.2.x is safe for schema extract.

Overview
Restores TypeGen stability by rolling the workspace catalog entry for @sanity/vanilla-extract-vite-plugin from ^0.2.0 back to ^0.1.1, after pnpm typegen / sanity schema extract began failing with module is not defined on the newer plugin.

pnpm-lock.yaml is refreshed so importers resolve 0.1.1 everywhere; the lockfile also reflects the older plugin’s dependency wiring (e.g. @vanilla-extract/integration instead of the 0.2.x integration package) and assorted transitive supports-color variant updates. No plugin or studio source changes.

^{Reviewed by Cursor Bugbot for commit 499e93d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
plugins-studio	Ready	Preview, Comment	Jul 16, 2026 1:12pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 499e93d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a 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/​@​sanity/​vanilla-extract-vite-plugin@​0.1.1

View full report

[Copilot]

Pull request overview

Restores CI TypeGen stability by rolling back the workspace catalog version of @sanity/vanilla-extract-vite-plugin (and the lockfile resolution) after pnpm typegen / schema extraction started failing with module is not defined on 0.2.x.

Changes:

• Reverted the workspace catalog entry for @sanity/vanilla-extract-vite-plugin from ^0.2.0 to ^0.1.1.
• Regenerated pnpm-lock.yaml so the resolved plugin version is 0.1.1 and the dependency graph is updated accordingly.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
pnpm-workspace.yaml	Rolls back the catalog range for @sanity/vanilla-extract-vite-plugin to avoid 0.2.x.
pnpm-lock.yaml	Updates the lockfile to resolve @sanity/vanilla-extract-vite-plugin to 0.1.1 and refreshes transitive resolution metadata.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.