fix(workbench): bind a user-pinned port strictly instead of drifting by gu-stav · Pull Request #1293 · sanity-io/cli

gu-stav · 2026-06-12T14:47:26Z

Description

Setting server: {port: 5555} in sanity.cli.ts doesn't pin the workbench dev server to that port — createWorkbenchViteServer hardcodes strictPort: false, so a busy port makes Vite silently drift to the next free one. A pinned port is a contract with external tooling (port allocators, proxies pointing at the URL), and the drift compounds: the app server stacks on workbenchPort + 1, so everything shifts off the allocated ports without a word.

getSharedServerConfig now reports whether the port was pinned (flag, env var, or server.port — the same chain that resolves the value), and the workbench server binds strictly when it was. A busy pinned port takes the existing fallback path: warn and run without a workbench rather than on the wrong port. The unconfigured 3333 default keeps the drift, same as before.

The app/studio dev server keeps its own non-strict behavior (getViteConfig decides that separately) — this only stops the workbench from squatting a neighboring port when the user asked for a specific one.

What to review

The httpPortConfigured derivation in getSharedServerConfig (pinned means the flag/env/config chain produced a value — an explicit 3333 counts), and the strictPort plumbing through devAction into createWorkbenchViteServer.

Testing

getSharedServerConfig.test.ts covers all 4 port sources, startWorkbenchDevServer.test.ts covers strict/non-strict vite config plus the busy-pinned-port fallback (lock released, warn, no workbench), and devAction.test.ts covers the plumbing both ways.

Note

Low Risk
Scoped to workbench dev port resolution in @sanity/cli; default unpinned behavior is preserved and app/studio servers are untouched.

Overview
Fixes workbench dev server ignoring user-pinned ports by no longer hardcoding Vite strictPort: false, which let a busy port drift silently and also misalign the app server on workbenchPort + 1.

getSharedServerConfig now exposes httpPortConfigured when the port comes from a flag, env var, or server.port in sanity.cli.ts (including an explicit 3333). devAction forwards that as strictPort into the workbench Vite server so a pinned port fails fast instead of drifting. If listen fails on a pinned port, behavior stays the same: warn, release the lock, and run without workbench so the studio/app can use the configured port. The implicit default 3333 still allows port drift.

App/studio dev server strictness is unchanged; only workbench binding is affected. New tests cover port-source detection, strict vs non-strict Vite config, busy pinned-port fallback, and devAction plumbing.

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

Co-authored-by: Josh <joshua.ellis18@gmail.com> fix(workbench): allow for a dynamic port (#830)

) * feat(dev): forward CLI config organization id to workbench runtime * chore: update auto-generated changeset for PR #905 --------- Co-authored-by: ecospark[bot] <ecospark[bot]@users.noreply.github.com>

Co-authored-by: Gustav Hansen <gustav.hansen@sanity.io>

…913) Pass `reactRefreshHost` to `@vitejs/plugin-react` so federated Studio modules connect their react-refresh preamble to the workbench host, enabling component-level HMR across the module federation boundary. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…#917)

* fix(dev): disable strict ports for applications * chore: update auto-generated changeset for PR #930 * fix: format * fix: format * chore: update tests --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

…ing local apps (#932)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix(workbench): propagate staging env to workbench dev server The workbench dev server was missing the `__SANITY_STAGING__` Vite define that the app/studio dev servers receive via `getViteConfig`. This meant `SANITY_INTERNAL_ENV=staging` had no effect on the workbench client bundle. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * chore: update auto-generated changeset for PR #964 --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

* fix(workbench): externalize sanity and @sanity/workbench * chore: update auto-generated changeset for PR #971 * chore: exclude .github from oxfmt format check Co-authored-by: Gustav Hansen <gu-stav@users.noreply.github.com> * fix: revert update changeset --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com> Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Gustav Hansen <gu-stav@users.noreply.github.com>

Co-authored-by: Gustav Hansen <gu-stav@users.noreply.github.com> Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com> Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>

* feat(init): add promt for federation * chore: update auto-generated changeset for PR #988 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

* fix: types * chore: update auto-generated changeset for PR #989 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* feat(workbench): extend local application payloads * fix: types * fix: pr feedback * chore: improve tests * fix: concise * fix: pr feedback

* feat(init): use `workbench` dist-tag for `sanity` package * chore: update auto-generated changeset for PR #992 * test: add unit tests --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

* fix(init): do not resolve dist tags * chore: update auto-generated changeset for PR #1000 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

* feat(dev): extract studio manifest and pass it for local applications * chore: update auto-generated changeset for PR #997 * fix: rework to use manifests for both * chore: update auto-generated changeset for PR #997 * fix: cleanup * chore: share cache dir constant * feat: extract manifest in background * fix: path resolution on windows * fix: pr feedback * fix: pr feedback --------- Co-Authored-By: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

* fix(workbench): remove warmup for dependencies * chore: update auto-generated changeset for PR #1047 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

…ench projects (#1259) * fix(build): restore strict-port for plain studio dev servers The workbench refactor hardcoded strictPort: false, so a plain studio on a busy port silently drifted to the next free one instead of failing like on main. Only apps and workbench runs need the fallback. * fix(dev): keep default signal handling for plain projects devAction installed SIGINT/SIGTERM handlers for every project, changing Ctrl-C semantics (and exit codes) for plain runs that have no workbench lock or registry entry to clean up. Only register them when workbench state exists. * fix(dev): only override the port flag when the workbench runs devAction pre-resolved the port and injected it into flags for every project, taking resolution away from getDevServerConfig where main does it. The override only exists so the app server can move off the port the workbench claimed — without a workbench the flags now pass through untouched. * chore: update auto-generated changeset for PR #1259 * chore: update auto-generated changeset for PR #1259 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

…ver (#1262) Everything the workbench vite server serves is either plain JS (the generated workbench.js), compiled dist (sanity/workbench), or TypeScript source that vite's own esbuild transforms (@sanity/workbench). plugin-react excludes node_modules from fast refresh, so it never transformed a single module here — its only output was a preamble script nothing consumed. Removing it also drops @vitejs/plugin-react from @sanity/cli's dependencies, keeping vite plugins contained to @sanity/cli-build.

…/cli re-exports (#1269)

…1270)

…#1267) * fix(dev): display localhost for non-routable workbench bind addresses sanity dev --host 0.0.0.0 printed http://0.0.0.0:3333 as the workbench URL — both for the binding process and for any process reusing the lock, which stores the bind host verbatim. 0.0.0.0/:: don't open in every browser (notably on Windows). Only the displayed URL is normalized; the bind address and lock contents are untouched. * chore: update auto-generated changeset for PR #1267 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

* feat(cli-build)!: require organizationId in unstable_defineApp unstable_defineApp is the workbench opt-in and the organization ID is what the workbench runs and deploys against, so it's part of the contract — required in the schema and the DefineAppInput/DefineAppResult types, with a pointed validation message. Ports sanity-io/workbench#250 to the vendored extension API. * chore: update auto-generated changeset for PR #1279 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

* fix(dev): release the workbench lock when server creation throws createWorkbenchViteServer can throw after the lock is acquired (runtime- file write failure, invalid remote URL); only the undefined-result path released it, so a throw leaked the lock file until the next acquire pruned the stale PID. * chore: update auto-generated changeset for PR #1266 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

Residue of the main sync after the rebase: the regenerated lockfile entries (sanity v6 fixture refs, @types/node 22 peer suffixes) and the organizationId brand on deploy.studio.test.ts's unstable_defineApp call required by #1279.

…rs (#1264) * fix(build): apply caller-provided vite plugins to workbench dev servers additionalPlugins (typegen in dev) was only spread into the non-workbench plugin branch, so typegen.enabled was silently ignored for workbench apps. The plugins aren't client-specific — hoist them out of the branch. * chore: update auto-generated changeset for PR #1264 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

…pp (#1265) unstable_defineApp is the workbench opt-in and carries the organization ID, so the fallback that resolved it from the configured project is gone — it needed an authenticated user (a logged-out sanity dev died on a raw auth error) and an API round-trip on every startup for something the opt-in already declares. A missing ID is now a readable error pointing at unstable_defineApp in sanity.cli.ts.

…cts (#1282)

* ci: revert snapshot-release.yml to main The branch had gutted the forceBump full-release half of the workflow and hardcoded the workbench dist-tag; merging that to main would have silently removed the manual release capability. Restoring main's file verbatim removes the merge delta entirely. Branch snapshots are published by dispatching the workflow manually with 'workbench' as the tag input — pushes to feat/workbench no longer auto-publish. * chore: curate the workbench changesets for the main changelog 40 accumulated changesets — auto-generated per-PR entries, superseded alpha bumps, and snapshot-publish-ordering notes — would have landed in the public changelog verbatim at merge. Squashed into three human-written entries; the resulting bump plan is unchanged (majors across the board, driven by main's Node 20 drop), so branch snapshot releases version identically.

… entry The dts change ships as part of the workbench feature; the curated workbench.md entry already covers it for the public changelog.

…1287) * fix(build): fail fast when a workbench studio has no sanity config An explicit applicationType: 'studio' wins over detection, so the federation studio path is reachable without a sanity.config file. The non-null assertion let null flow into the generated remote entry, which then imports its config from "null" — a broken build with no hint at the cause. * chore: update auto-generated changeset for PR #1287 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

…1284) * fix(workbench): stop wiping studio interfaces from the dev registry The studio extract hardcoded interfaces: undefined while the registry patch is a shallow merge — the panels/workers forwarded by the initial registration were wiped on the first regeneration, which fires right at watcher startup. Re-derive them from a fresh config read, the way the core-app extract already does. * chore: update auto-generated changeset for PR #1284 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

debug is imported in getViteConfig.ts for type checking only; without the ignore knip flags @types/debug as unused once dependencies shift.

* revert(workbench): keep federated remote type generation off Reverts the behavior change from #1282. Real TS apps fail with TYPE-001: the exposes are generated .js/.jsx shims, which tsc refuses without allowJs (TS6504) — no app template sets it. With allowJs worked around, declaration emit pulls in the user's own noEmit app code, which was never written to be declaration-emittable (TS2742 non-portable inferred types under pnpm, TS4082 private names in default exports). The #1282 verification only passed because the federated-studio fixture set allowJs — removed here so the fixture matches real templates. The recursive plugin scoping from #1282 stays: it's correct regardless. * chore: update auto-generated changeset for PR #1288 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

…anges (#1286) * fix(workbench): rebuild federated studios when their interface set changes Studios declare views/services in unstable_defineApp like apps do, but the dev flow assumed they couldn't: no rebuild hook, and the manifest watcher only reacted to sanity.config.* (the resolved project root) while the declarations live in sanity.cli.*. Adding or removing a studio view/service required a manual dev-server restart to get an expose for it. * chore: update auto-generated changeset for PR #1286 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

github-actions · 2026-06-12T14:48:01Z

📦 Bundle Stats — `@sanity/cli`

Compared against feat/workbench (5a424922)

`@sanity/cli`

Metric	Value	vs feat/workbench (`5a42492`)
Internal (raw)	2.7 KB	-
Internal (gzip)	1.1 KB	-
Bundled (raw)	11.15 MB	-
Bundled (gzip)	2.10 MB	-
Import time	908ms	+34ms, +3.9%

`bin:sanity`

Metric	Value	vs feat/workbench (`5a42492`)
Internal (raw)	782 B	-
Internal (gzip)	423 B	-
Bundled (raw)	9.87 MB	-
Bundled (gzip)	1.77 MB	-
Import time	2.12s	+65ms, +3.1%

🗺️ View treemap · Artifacts

Details

Import time regressions over 10% are flagged with ⚠️
Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

📦 Bundle Stats — `@sanity/cli-core`

Compared against feat/workbench (5a424922)

Metric	Value	vs feat/workbench (`5a42492`)
Internal (raw)	105.5 KB	-
Internal (gzip)	25.8 KB	-
Bundled (raw)	21.71 MB	-
Bundled (gzip)	3.45 MB	-
Import time	796ms	-34ms, -4.1%

🗺️ View treemap · Artifacts

Details

Import time regressions over 10% are flagged with ⚠️
Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

📦 Bundle Stats — `create-sanity`

Compared against feat/workbench (5a424922)

Metric	Value	vs feat/workbench (`5a42492`)
Internal (raw)	908 B	-
Internal (gzip)	483 B	-
Bundled (raw)	931 B	-
Bundled (gzip)	491 B	-
Import time	❌ ChildProcess denied: node	-

Details

Import time regressions over 10% are flagged with ⚠️
Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

github-actions · 2026-06-12T14:49:55Z

Preview this PR with pkg.pr.new

Run the Sanity CLI

npx https://pkg.pr.new/sanity-io/cli/@sanity/cli@a02385c <command>

...Or upgrade project dependencies

📦 `@sanity/cli`

pnpm install https://pkg.pr.new/@sanity/cli@a02385c

📦 `@sanity/cli-build`

pnpm install https://pkg.pr.new/@sanity/cli-build@a02385c

📦 `@sanity/cli-core`

pnpm install https://pkg.pr.new/@sanity/cli-core@a02385c

📦 `@sanity/cli-test`

pnpm install https://pkg.pr.new/@sanity/cli-test@a02385c

📦 `@sanity/eslint-config-cli`

pnpm install https://pkg.pr.new/@sanity/eslint-config-cli@a02385c

View Commit (a02385c)

joshuaellis · 2026-06-12T14:56:26Z

what is the actual problem here, the description is quite waffle-y and im not getting it – is it that you set port X but if it isn't available it disregards it? if so why dont we just bail like the studio does if we feel that strongly about it adhering to the port the user has chosen?

github-actions · 2026-06-12T15:01:25Z

Coverage Delta

File	Statements
packages/@sanity/cli-build/src/actions/build/getEntryModule.ts	100.0% (±0%)
packages/@sanity/cli-build/src/actions/build/getViteConfig.ts	100.0% (±0%)
packages/@sanity/cli-build/src/actions/build/writeSanityRuntime.ts	96.2% (+ 0.7%)
packages/@sanity/cli-build/src/workbench/artifact.ts	60.0% (new)
packages/@sanity/cli-build/src/workbench/contract.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/defineApp.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/defineService.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/defineView.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/render-remote.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/services/artifact.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/views/artifact.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/vite/constants.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/vite/plugin.ts	90.0% (new)
packages/@sanity/cli-build/src/workbench/vite/plugins/plugin-module-federation.ts	92.8% (new)
packages/@sanity/cli-build/src/workbench/vite/plugins/plugin-sanity-environment.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/vite/plugins/plugin-sanity-extension-artifacts.ts	100.0% (new)
packages/@sanity/cli-build/src/workbench/vite/plugins/plugin-sanity-federation-runtime.ts	34.3% (new)
packages/@sanity/cli-build/src/workbench/vite/utils/invariant.ts	50.0% (new)
packages/@sanity/cli-core/src/config/cli/getCliConfig.ts	100.0% (±0%)
packages/@sanity/cli-core/src/config/cli/getCliConfigSync.ts	81.0% (+ 38.9%)
packages/@sanity/cli-core/src/config/cli/workbenchApp.ts	100.0% (new)
packages/@sanity/cli-core/src/services/cliUserConfig.ts	100.0% (±0%)
packages/@sanity/cli-core/src/util/getSanityConfigDir.ts	66.7% (new)
packages/@sanity/cli/src/actions/build/buildApp.ts	95.4% (+ 0.1%)
packages/@sanity/cli/src/actions/build/buildStaticFiles.ts	97.7% (+ 0.9%)
packages/@sanity/cli/src/actions/build/buildStudio.ts	96.7% (+ 0.1%)
packages/@sanity/cli/src/actions/deploy/deployApp.ts	73.6% (- 7.0%)
packages/@sanity/cli/src/actions/deploy/deployStudio.ts	91.7% (- 0.8%)
packages/@sanity/cli/src/actions/deploy/viewDeployment.ts	66.7% (new)
packages/@sanity/cli/src/actions/deploy/workbenchChecks.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/devAction.ts	97.5% (- 2.5%)
packages/@sanity/cli/src/actions/dev/registration/deriveInterfaces.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/registration/extractDevServerManifest.ts	20.0% (new)
packages/@sanity/cli/src/actions/dev/registration/interfaceSetId.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/registration/startDevManifestWatcher.ts	90.9% (new)
packages/@sanity/cli/src/actions/dev/registration/startDevServerRegistration.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/registry/processLiveness.ts	89.7% (new)
packages/@sanity/cli/src/actions/dev/registry/registry.ts	93.6% (new)
packages/@sanity/cli/src/actions/dev/registry/workbenchLock.ts	97.7% (new)
packages/@sanity/cli/src/actions/dev/servers/getDashboardAppUrl.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/servers/getDevServerConfig.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/servers/startAppDevServer.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/servers/startStudioDevServer.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/shared/canonicalizeWatchDir.ts	100.0% (new)
packages/@sanity/cli/src/actions/dev/workbench/startWorkbenchDevServer.ts	98.8% (new)
packages/@sanity/cli/src/actions/dev/workbench/writeWorkbenchRuntime.ts	100.0% (new)
packages/@sanity/cli/src/actions/init/bootstrapLocalTemplate.ts	89.7% (±0%)
packages/@sanity/cli/src/actions/init/bootstrapTemplate.ts	0.0% (±0%)
packages/@sanity/cli/src/actions/init/createAppCliConfig.ts	100.0% (±0%)
packages/@sanity/cli/src/actions/init/createCliConfig.ts	100.0% (+ 50.0%)
packages/@sanity/cli/src/actions/init/createStudioConfig.ts	83.3% (±0%)
packages/@sanity/cli/src/actions/init/initAction.ts	93.3% (+ 0.1%)
packages/@sanity/cli/src/actions/init/initApp.ts	96.0% (±0%)
packages/@sanity/cli/src/actions/init/initStudio.ts	87.0% (±0%)
packages/@sanity/cli/src/actions/init/scaffoldTemplate.ts	100.0% (±0%)
packages/@sanity/cli/src/actions/init/types.ts	100.0% (±0%)
packages/@sanity/cli/src/actions/manifest/extractCoreAppManifest.ts	93.9% (new)
packages/@sanity/cli/src/actions/manifest/extractManifest.ts	6.3% (+ 6.3%)
packages/@sanity/cli/src/actions/manifest/iconResolver.tsx	100.0% (±0%)
packages/@sanity/cli/src/actions/manifest/sanitizeIcon.ts	100.0% (new)
packages/@sanity/cli/src/actions/manifest/types.ts	100.0% (±0%)
packages/@sanity/cli/src/actions/manifest/writeManifestFile.ts	22.2% (+ 22.2%)
packages/@sanity/cli/src/commands/dev.ts	100.0% (±0%)
packages/@sanity/cli/src/commands/init.ts	100.0% (±0%)
packages/@sanity/cli/src/commands/manifest/extract.ts	0.0% (±0%)
packages/@sanity/cli/src/server/devServer.ts	94.4% (±0%)
packages/@sanity/cli/src/util/determineIsApp.ts	100.0% (±0%)
packages/@sanity/cli/src/util/getSharedServerConfig.ts	100.0% (±0%)
packages/@sanity/cli/src/util/resolveReactStrictMode.ts	100.0% (new)

Comparing 69 changed files against main @ fe61c5dd97f3e5c02352bace830d15fb0180cfcc

Overall Coverage

Metric	Coverage
Statements	81.9% (+ 1.1%)
Branches	73.5% (+ 1.1%)
Functions	81.8% (+ 2.5%)
Lines	82.4% (+ 1.1%)

gu-stav and others added 30 commits June 12, 2026 11:36

feat: workbench dev server (#770)

490c32d

Co-authored-by: Josh <joshua.ellis18@gmail.com> fix(workbench): allow for a dynamic port (#830)

feat(dev): forward CLI config organization id to workbench runtime (#905

0125e4c

) * feat(dev): forward CLI config organization id to workbench runtime * chore: update auto-generated changeset for PR #905 --------- Co-authored-by: ecospark[bot] <ecospark[bot]@users.noreply.github.com>

feat: add federation vite plugin (#826)

cf982b7

Co-authored-by: Gustav Hansen <gustav.hansen@sanity.io>

feat: improve warmup files when federation is enabled (#906)

ede5192

chore(deps): bump @sanity/federation from 0.1.0-alpha.2 to 0.1.0-alpha.3

6b16e73

fix(workbench): require sanity/workbench and no @sanity/workbench (…

a9a6281

…#917)

feat(federation): pass additional props to federation plugin (#918)

7d57fe3

chore: add changeset for cli-core

221e03f

ci: auto-release dist tag for feature branch (#931)

38d36a7

feat(workbench): support only running one workbench instance and find…

8d96335

…ing local apps (#932)

fix: remove load-in-dashboard flag from dev command

aac4761

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: update snapshot release workflow (#965)

e45b0b4

chore(workflow): ensure we NEVER have the ability to do PROD release

28cdf82

fix(federation): align fixture react/styled-components with main

b8195dc

feat(workbench): resolve organization id from project [SDK-1277] (#973)

819da10

feat(init): add promt for federation (#988)

e41c4da

* feat(init): add promt for federation * chore: update auto-generated changeset for PR #988 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

fix(init): types for federation prompt (#989)

fe50a1f

* fix: types * chore: update auto-generated changeset for PR #989 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

chore(cli): bump @sanity/federation to 0.1.0-alpha.6 (#990)

0520d62

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

feat(workbench): extend local application payloads (#987)

39b14d4

* feat(workbench): extend local application payloads * fix: types * fix: pr feedback * chore: improve tests * fix: concise * fix: pr feedback

fix(init): do not resolve dist tags (#1000)

569e45f

* fix(init): do not resolve dist tags * chore: update auto-generated changeset for PR #1000 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

fix: recover workbench rebase

bdfbda1

fix(cli): apply user vite config to federation builds [SDK-1281] (#1005)

a833b50

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

fix(workbench): remove warmup for dependencies (#1047)

ecb1105

* fix(workbench): remove warmup for dependencies * chore: update auto-generated changeset for PR #1047 --------- Co-authored-by: squiggler-app[bot] <265501495+squiggler-app[bot]@users.noreply.github.com>

gu-stav and others added 19 commits June 12, 2026 11:37

refactor(cli-build): own the module-federation extension API; @sanity…

1ace0b5

…/cli re-exports (#1269)

refactor(cli-build): move the module-federation vite plugin in-tree (#…

03514bb

…1270)

feat(workbench): generate federated remote types for TypeScript proje…

418fcf5

…cts (#1282)

chore(workbench): fold the #1282 changeset into the curated workbench…

233cdfc

… entry The dts change ships as part of the workbench feature; the curated workbench.md entry already covers it for the public changelog.

chore(knip): restore the @types/debug ignore for cli-build (#1283)

c8ec988

debug is imported in getViteConfig.ts for type checking only; without the ignore knip flags @types/debug as unused once dependencies shift.

fix(workbench): bind a user-pinned port strictly instead of drifting

3275b62

gu-stav requested a review from a team as a code owner June 12, 2026 14:47

chore: update auto-generated changeset for PR #1293

a02385c

gu-stav requested a review from joshuaellis June 12, 2026 14:49

gu-stav added the trigger: preview label Jun 12, 2026

joshuaellis approved these changes Jun 12, 2026

View reviewed changes

gu-stav force-pushed the feat/workbench branch 2 times, most recently from 80854d6 to f5283f9 Compare June 16, 2026 07:26

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(workbench): bind a user-pinned port strictly instead of drifting#1293

fix(workbench): bind a user-pinned port strictly instead of drifting#1293
gu-stav wants to merge 79 commits into
feat/workbenchfrom
fix/workbench-strict-port

gu-stav commented Jun 12, 2026 •

edited by cursor Bot

Loading

Uh oh!

github-actions Bot commented Jun 12, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jun 12, 2026

Uh oh!

joshuaellis commented Jun 12, 2026

Uh oh!

github-actions Bot commented Jun 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

gu-stav commented Jun 12, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

What to review

Testing

Uh oh!

github-actions Bot commented Jun 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📦 Bundle Stats — @sanity/cli

@sanity/cli

bin:sanity

📦 Bundle Stats — @sanity/cli-core

📦 Bundle Stats — create-sanity

Uh oh!

github-actions Bot commented Jun 12, 2026

Preview this PR with pkg.pr.new

Run the Sanity CLI

...Or upgrade project dependencies

📦 @sanity/cli

📦 @sanity/cli-build

📦 @sanity/cli-core

📦 @sanity/cli-test

📦 @sanity/eslint-config-cli

Uh oh!

joshuaellis commented Jun 12, 2026

Uh oh!

github-actions Bot commented Jun 12, 2026

Coverage Delta

Overall Coverage

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

gu-stav commented Jun 12, 2026 •

edited by cursor Bot

Loading

github-actions Bot commented Jun 12, 2026 •

edited

Loading

📦 Bundle Stats — `@sanity/cli`

`@sanity/cli`

`bin:sanity`

📦 Bundle Stats — `@sanity/cli-core`

📦 Bundle Stats — `create-sanity`

📦 `@sanity/cli`

📦 `@sanity/cli-build`

📦 `@sanity/cli-core`

📦 `@sanity/cli-test`

📦 `@sanity/eslint-config-cli`