$ cat supabase/week/2026-09-14.log
the week in review · Sep 14 – Sep 20, 2026
Studio moves to Nitro, CLI stack goes flag-gated
By RepoJournal · composed from the cited sources · human-reviewed weekly · methodology
Supabase's week split three ways: self-hosting artifacts, experimental CLI stack controls, and a TypeScript server rewrite.
chore(studio): move the TanStack Start deploy onto Nitro (#50030) supabase/supabase
The hand-rolled Vercel setup (api/server.js shim, vercel.ts rewrites, the custom ?dpl= skew-protection Vite plugin, and scripts/serve.js for self-hosted) is gone, replaced by Nitro. If you self-host Studio, your server entrypoint changes, so read the new build output before your next deploy.
feat(replicator): Add configurable activity health probes supabase/etl
The replicator gains opt-in health endpoints and Kubernetes probes, tracking activity separately for each WAL apply/catchup loop and each initial table copy. A stalled replication job can now make its Pod unready and, after configured failures, trigger a restart instead of sitting there silently.
fix(cli): gate stack commands behind experimental flag supabase/cli
supabase stack was registered unconditionally and bypassed feature-flag resolution. It now appears only when experimental.stack is enabled, including in help and completion, while top-level start and stop fall back to the legacy implementations when the flag is off.
feat(cli): add experimental stack status supabase/cli
With experimental.stack set (or SUPABASE_EXPERIMENTAL_STACK=1), supabase status and supabase stack status run the same implementation and can export connection variables. With the flag off, the stack command group stays absent.
fix(cli): report functions serve outcomes from real container state (CLI-2426) (#6594) supabase/cli
functions serve reported almost every session as a failure, and few of those failures carried a usable classification. It now reads real container state, so your local function output should stop crying wolf.
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 and db.seed, the config-side realtime.* fields, and local-only experimental.* selectors) are excluded from ProjectConfig's type and schema, so config tooling stops treating local-only keys as project config.
storage v1.79.4 supabase/slim-services
Portable, smoke-tested runtime artifacts ship for storage v1.79.4 across linux/amd64, linux/arm64, and darwin/arm64, with the multi-platform image at ghcr.io/supabase/cli/storage:v1.79.4. The image reference is immutable via a sha256 digest, which is what you want pinned in production compose files.
feat: support skip_elicitations in the local HTTP server supabase/mcp
The local HTTP server can now skip cost elicitations per tool via skip_elicitations. Alongside: the Studio SQL Editor gained column-name auto-completion beyond the . operator, and Warehouse connection methods were polished so enabling Warehouse no longer silently enables DuckDB catalogue access.
$ ls supabase/week/ # the briefings behind this review
Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.
Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.