$ the-wire · showcase
Pipeline wizard validation closes gaps, Realtime stops unnecessary partition locks
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
Studio's pipeline wizard now rejects invalid destinations and data settings before Review, while Realtime 2.145 gains a presence track latency metric and 2.145.2 packages it for deployment.
feat(studio): validate pipeline wizard connections supabase/supabase
The wizard previously let users press Continue without valid destination credentials; it now validates all four destinations against the existing schemas on Continue and advances to Data only on success, showing field errors and connection failures inline and pausing on warnings. A connection settings change forces a re-check, so a previously passing test no longer counts.
feat(studio): validate pipeline wizard data settings supabase/supabase
Users could reach Review with an unavailable publication or removed initial-sync tables. Both are now rejected, invalid data settings are revealed with values preserved for retry, and browser-history shortcuts to Review are blocked once data settings change.
fix(studio): guard unsaved pipeline creation navigation supabase/supabase
Unsaved pipeline changes were only guarded against a subset of exits; TanStack confirmation now covers client-side navigation including Back and Forward, Close and header links go through the discard dialog, and refresh falls back to the browser warning. Step changes still do not prompt, and Next.js router exits remain outside this slice.
fix: alter ownership on new partitions only supabase/realtime
Realtime now runs ALTER TABLE ... OWNER TO supabase_realtime_admin only on new partitions and creates only partitions that do not exist, removing locks the migration did not need.
v2.145.0 supabase/realtime
Realtime 2.145.0 adds a metric for presence track latency on the local call, complementing the existing presence notification latency that measures how long the diff took to reach subscribers. slim-services shipped it as realtime v2.145.2-r0 for linux/amd64, linux/arm64 and darwin/arm64 alongside studio 2026.10.19-sha-b375769-r0.
fix: pick single broadcast payload type from Content-Type supabase/realtime
The single broadcast endpoint chose JSON or binary by looking for a "_binary" key in body_params, so a JSON object carrying that key went out as binary and a non-object JSON body was wrapped as {"_json": ...}. The raw octet-stream body now lives in conn.private[:realtime_binary_body], the controller reads it there, and non-object JSON bodies return 422 to match the schema.
