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-06-14
stories 8

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

REALTIME SHIPPING LOGGING FIX, SELF-HOSTED SHELL ALIGNMENT LANDS

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

Realtime v2.107.2 improves observability into publication changes while self-hosted deployments align their shell execution layer.

Realtime shipped v2.107.2 [1] with a logging fix [2] that surfaces publication changes on the Poller, making it easier to debug what's actually happening in your subscriptions. The release follows a pattern-setting week on the realtime desk where connection settling logic [3] landed before publication visibility improvements. On the self-hosted front, the Kong entrypoint script got aligned to use /bin/sh shebang [4] [5] instead of /bin/bash, matching what the compose file actually invokes. This is a small but important consistency fix that prevents future confusion in containerized deployments. Both changes represent the kind of operational polish that prevents debugging headaches down the line.

Quick answers

What shipped in Supabase on June 14, 2026?
Realtime v2.107.2 improves observability into publication changes while self-hosted deployments align their shell execution layer. In total, 4 commits, 3 pull requests, and 1 releases landed.
Who contributed to Supabase on June 14, 2026?
3 developers shipped this update, including edgurgel, filipecabaco, and singh-inder.
What were the notable Supabase updates?
v2.107.2, fix: log when publication changes on Poller, and chore: let the connection settle before db action.