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-09-28
stories 45

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Auth starts with zero session limits, Realtime holds the pool open

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

Two long-standing boot and shutdown failures got closed out today, one in the CLI stack and one in Realtime, alongside a narrower queue target for the subscriptions pool.

fix(stack): start auth with zero session limits (CLI-2506) (#6848) supabase/cli

by Vaibhav

`supabase start` used to forward `0s` for `timebox` or `inactivity_timeout` straight into the auth container, which rejects a zero duration and exited on boot, leaving every auth request returning 502. Zero values are now simply left out of the auth environment, so `0s` means no limit while every other value passes through unchanged.

fix: keep Connect alive when a user rejoins during idle shutdown supabase/realtime

by hsusul

Connect's idle checker fills an 11-sample zero bucket and then stops sampling `UsersCounter`, but still fires `:shutdown_no_connected_users` one interval later, so a client that joins inside that window is counted and then torn down anyway. The shutdown kills the tenant database pool and the `realtime.messages` replication connection underneath a live websocket, and database broadcasts stay dow...

fix: reduce queue target on subs pool supabase/realtime

by edgurgel

Saturated subscriptions pools now reply sooner rather than waiting out the full queue target, so RPC calls hit fewer timeouts when the pool is under pressure.

fix: track a join rejected for an empty topic name supabase/realtime

by hsusul

Every join with the empty topic name `realtime:` was rejected before `Tracker.track/1` ran, yet `terminate/2` still called `Tracker.untrack/2`, quietly decrementing the transport pid's counter. The join is now tracked so the untrack is balanced.

v17.6.1.178-cli supabase/postgres

by github-actions[bot]

The `v17.6.1.178-cli` release rescopes the pg_graphql and pg_cron event triggers during pg_upgrade and bumps supautils to 3.4.4, the kind of change that matters when you are moving a database across major versions.

docs(pipelines): improve Snowflake setup guidance supabase/supabase

by dnywh

Quieter desks: Studio's Assistant now allows longer responses and surfaces timeouts instead of spinning forever, the Snowflake pipeline guide spells out roles and RSA key placement, and postgres cut the 15.14.1.178 and 17.11.0.002-orioledb builds.

Quick answers

What shipped in Supabase on September 28, 2026?
Two long-standing boot and shutdown failures got closed out today, one in the CLI stack and one in Realtime, alongside a narrower queue target for the subscriptions pool. In total, 18 commits, 16 pull requests, and 11 releases landed.
Who contributed to Supabase on September 28, 2026?
7 developers shipped this update, including wendeh, dnywh, SaxonF, Vaibhav, edgurgel, hsusul, and github-actions[bot].
What were the notable Supabase updates?
fix(stack): start auth with zero session limits (CLI-2506) (#6848), fix: keep Connect alive when a user rejoins during idle shutdown, and fix: reduce queue target on subs pool.