151 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

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.

$ status

wire 2026-10-05
stories 22

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Loopback bind addresses for native CLI stacks, auto region selection experiment retired

By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology

The day's substantive work is in slim-services, where native no-Docker CLI stacks gain per-service bind address control and studio, realtime, analytics, and pooler all get fresh smoke-tested artifacts; the studio desk is visual polish and cleanup.

feat(native): accept a loopback bind address for realtime, pooler, and analytics supabase/slim-services

by jgoux

Native (no-Docker) CLI stacks need every service on loopback only, but Realtime's HTTP endpoint, Supavisor's admin endpoint and proxy listeners, and Logflare's gRPC server had no bind-address setting and always listened on every interface, which is reachable from the LAN and on macOS can be silently shadowed. One opt-in env var per service is added; when it is unset, each service binds exactly ...

Clean up auto region selection experiment supabase/supabase

by joshenlim

The auto region selection experiment is removed, so project creation no longer offers a "Best available" region: you pick a specific region or a smart group, and the selected region name appears in the selector. The associated ConfigCat feature flag can now be cleaned up.

feat(docs): render experimental badge for Management API endpoints supabase/supabase

by Johan Bergström

Management API endpoints can now be marked as experimental rather than only deprecated, and the docs render an experimental badge in place of the strikethrough, signalling the endpoint is being tested for inclusion rather than slated for removal.

fix(studio): drop brand override on last-used sign-in badge (#51248) supabase/supabase

by Danny White

The Studio "Last used" badge on the sign-in screen had overridden Badge variant="success" with bg-brand-400, which read as lime in light mode rather than success green. The colour override is dropped, with no new Badge variant and no other callsite churn.

Joshenlim/fe 4522 polish recovery codes UI (#51124) supabase/supabase

by Joshen Lim

The recovery codes section under Account settings -> Security moves below MFA, since recovery codes only matter after an MFA app is added, which also prevents layout shift under the feature flag. Visual only, no functional changes.

studio 2026.10.05-sha-94b8b06-r0 supabase/slim-services

by github-actions[bot]

Studio 2026.10.05-sha-94b8b06-r0, along with realtime v2.140.7-r1, analytics v1.50.15-r1, and pooler v2.9.13-r1, landed as portable smoke-tested artifacts for linux/amd64, linux/arm64, and darwin/arm64, each published as a multi-platform image under ghcr.io/supabase/cli with an immutable digest reference for pinning.

Quick answers

What shipped in Supabase on October 5, 2026?
The day's substantive work is in slim-services, where native no-Docker CLI stacks gain per-service bind address control and studio, realtime, analytics, and pooler all get fresh smoke-tested artifacts; the studio desk is visual polish and cleanup. In total, 9 commits, 9 pull requests, and 4 releases landed.
Who contributed to Supabase on October 5, 2026?
5 developers shipped this update, including Joshen Lim, Johan Bergström, Danny White, github-actions[bot], and jgoux.
What were the notable Supabase updates?
feat(native): accept a loopback bind address for realtime, pooler, and analytics, Clean up auto region selection experiment, and feat(docs): render experimental badge for Management API endpoints.