RepoJournal
Supabase @supabase
124 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-05-25
stories 14
GitHub RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

SUPABASE REALTIME SHIPS BINARY PAYLOAD SUPPORT, TABLE EDITOR FIXES DATA EXPORT BUG

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

joshenlim edgurgel taimoorzaeem
3 people shipped this
joshenlim @joshenlim 2 cited edgurgel @edgurgel 1 cited taimoorzaeem @taimoorzaeem 1 cited

Realtime v2.98.0 adds binary message handling to realtime.messages, while the dashboard table editor now correctly exports large column values that previously got truncated.

Supabase Realtime shipped v2.98.0 with native support for binary payloads in realtime.messages [1]. The feature adds a `binary_payload` column and overloads `realtime.send` to accept bytea, letting you push raw bytes through your subscription channels instead of always JSON-serializing [2]. This opens the door to lower-overhead media streaming and binary protocol work. The implementation uses a constraint to prevent both `binary_payload` and `payload` from being non-null simultaneously, keeping data integrity clean.

Meanwhile, the dashboard table editor had a data loss footgun. When you copied or exported selected rows containing values over 10,240 characters, the UI truncated those values for performance, but the export still used the truncated version instead of fetching the full value [3]. That's fixed now. On the UX side, the Connect Sheet now persists your authentication preferences to local storage, so reopening it remembers which parameters you selected last time [4]. Documentation also got clarified around SSO identity linking constraints [5].

Realtime also fixed a subtle JWT parsing bug where decimal numbers in `exp` and `iat` claims caused channels to close unexpectedly [6]. The fix rounds those claims to integers before validation.

$ ls supabase/reviews/ # the step-back reads

the week in review Studio moves to Nitro, CLI stack goes flag-gated the month in review Supabase ships CLI v2, Postgres middleware, and safety rails across Studio
Topics: JavaScript Full archive → Weekly reviews →

Quick answers

What shipped in Supabase on May 25, 2026?
Realtime v2.98.0 adds binary message handling to realtime.messages, while the dashboard table editor now correctly exports large column values that previously got truncated. In total, 7 commits, 5 pull requests, and 2 releases landed.
Who contributed to Supabase on May 25, 2026?
3 developers shipped this update, including edgurgel, joshenlim, and taimoorzaeem.
What were the notable Supabase updates?
v2.98.0, feat: add support to realtime.messages binary payloads, and Fix copy / export large values in table editor.
♥

$ log @supabase --recent

Turbopack build cache disabled, eval results refreshed 4 shipped CLI config push stops ignoring a piped "no"; storage and realtime artifacts refresh 70 shipped MCP v0.13.0 gates destructive SQL, CLI stops deleting vector buckets 113 shipped Replicator health probes land, Studio pipeline overview rebuilt 135 shipped

$ log --all # elsewhere on the wire

@openclaw Cold-start Gateway diagnostics stop crying wolf, doctor repairs plugin drift Agentic Coding Cline desktop bundles shrink, goose unblocks its own clicks

$ ls showcases/

Rails Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.