RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

  1. Sat 2 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

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

By RepoJournal · Filed · About Supabase

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.

Action items

References

  1. [1] v2.98.0 ↗ supabase/realtime
  2. [2] feat: add support to realtime.messages binary payloads ↗ supabase/realtime
  3. [3] Fix copy / export large values in table editor ↗ supabase/supabase
  4. [4] Persist connect sheet user preference ↗ supabase/supabase
  5. [5] chore(docs): Clarify identity linking for SSO (#46273) supabase/supabase
  6. [6] fix: channels closing when jwt claims contain decimal number ↗ supabase/realtime

FAQ

What changed 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.
What should Supabase teams do about it?
Deploy dashboard table editor fix before your next content import • Plan upgrade to Realtime v2.98.0 if you need binary message support • Monitor Realtime deployments for the JWT decimal fix if you use custom claims
Which Supabase repositories shipped on May 25, 2026?
supabase/realtime, supabase/supabase

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.