$ the-wire · showcase
Realtime throttles token refreshes, ETL makes shutdown explicit
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
Today's changes are all about control: Realtime pulls back on access token refresh frequency, ETL replaces a lossy watch-based shutdown channel with a retained cancellation token, and Studio drops the Classic Dark theme.
fix: throttle access token refreshing supabase/realtime
Realtime stops refreshing access tokens as aggressively as it did; clients that were re-authenticating on a tight cadence now do so less often. The same fix landed on main as commit d91b7b2.
ref(core): Improve shutdown handling supabase/etl
The ETL pipeline, replicator, destinations, and background tasks now have explicit shutdown ownership: a request stops new replication intake, and the owner finishes or cancels its work and joins the tasks it owns. The watch-based channel is gone in favor of a retained CancellationToken, so shutdown requests made before workers subscribe are no longer dropped, and Pipeline::shutdown() is the en...
chore(ui): remove the Classic Dark theme supabase/supabase
Classic Dark is removed from shared theme options, application commands, stylesheets, previews, examples, and replay handling, along with the Classic Dark and faux Classic Dark assets. Studio's supported modes are now System, Dark, and Light, and any app still resolving the old theme name will find it gone.
feat(studio): show table WAL retention headroom supabase/supabase
Replicated table rows in Studio now show the temporary sync slot's WAL retention headroom alongside the existing pending bytes, WAL risk, and last check-in. Finite values render as compact byte values and an explicit unlimited value is labeled "Unlimited WAL retention".
fix(auth): return 401 on a malformed authorization header (#2245) supabase/realtime
Realtime now answers 401 when an authorization header is malformed instead of treating it as valid, and in the long tail: Realtime closes the tenant version connection and tears down every replication slot rather than a single one, the docs replication guides were reorganized around current Pipelines behavior, and a new PostHog event tracks prompt panel copies on the docs homepage.
