$ the-wire · showcase
Studio moves onto Nitro, CLI drops the legacy compute bridge
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
15 people shipped this
Alaister Young
@alaister
1 cited
jordienr
@jordienr
1 cited
mattrossman
@mattrossman
1 cited
Miranda Limonczenko
@czenko
1 cited
barryroodt
@barryroodt
1 cited
Colum Ferry
@Coly010
1 cited
Raúl Barroso
@raulb
ivasilov
@ivasilov
supabase-evals-releaser
@supabase-evals-releaser
supabase-releaser
@supabase-releaser
supabase-releaser[bot]
@supabase-releaser[bot]
Julien Goux
@jgoux
Matt Johnston
@johnstonmatt
kanad
@kanadgupta
github-actions[bot]
@github-actions[bot]
Supabase's clients are converging on the renamed /compute management routes and a standard deployment path, which means anything pinned to the old /workers contract needs to move.
chore(studio): move the TanStack Start deploy onto Nitro (#50030) supabase/supabase
Studio's TanStack Start build drops the hand-rolled Vercel setup (api/server.js, rewrites in vercel.ts, the ?dpl= skew-protection Vite plugin, scripts/serve.js) for Nitro, TanStack Start's documented deployment path. Documents now serve from the static SPA shell on the CDN; only /api/* and /_serverFn/* hit the function, and self-hosted setups must pick up the Nitro build instead of scripts/serv...
fix(studio): use Compute management endpoints FUNC-896 supabase/supabase
Studio was still calling the legacy /workers Management API routes and parsing the old project_worker response shape, so Compute instances could not be listed or retrieved at all. The fix regenerates the v1, v2, and platform declarations from the deployed schemas and moves list and detail queries to /compute.
feat(config): exclude local-only paths from ProjectConfig's type and schema (#6639) supabase/cli
DOCUMENT_ONLY_LOCAL_PATHS (local bind ports and TLS, api.external_url, db.pooler.enabled/port, db.migrations, db.seed, every config-side realtime.* field, local-only experimental.* engine selection) was only stripped by fromConfigDocument at runtime. The ProjectConfig type, ProjectConfigSchema, and toProjectConfigJsonSchema() are now built without those paths, so locally valid config no longer ...
feat: support skip_elicitations in the local HTTP server supabase/mcp
The local HTTP server accepts a skip_elicitations CSV parameter carrying create_project and/or create_branch, with whitespace trimmed and empty entries ignored, letting local callers opt out of cost elicitations per tool the same way the platform API does. This is the MCP package's first feature since its management API types were regenerated from the current v1 and v2 OpenAPI specs.
fix(core): read a Codex `other` web_search action as a page read (#286) supabase/evals
Docs evals failed almost universally on the check that the agent retrieved a referenced page with content, because Codex round-trips openPage and findInPage through a snake_case enum with no such variants, so both arrive as other. Since docs evals run only on Codex, an explicit other is treated as positive evidence of a page read.
chore: upgrade @supabase/lite to 0.10.0 supabase/evals
Everything else was housekeeping: evals moved to @supabase/lite 0.10.0, which now ships most of the storage schema so platform-lite only patches role grants, while the CLI landed a vitest bump with a slim top-level config, a knip config that leans on plugin defaults, refreshed rules against 61 lint suppressions, and realtime v2.135.5 and storage v1.77.4 runtime artifacts.
