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-07-20
stories 11
GitHub RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

SUPABASE SHIPS CLICKHOUSE REPLICATION AND HARDENS CUSTOM AUTH

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

jmqd Joshen Lim danielmitterdorfer Eduardo Gurgel SaxonF github-actions[bot]
6 people shipped this
jmqd @jmqd 1 cited Joshen Lim @joshenlim 1 cited danielmitterdorfer @danielmitterdorfer 1 cited Eduardo Gurgel @edgurgel 1 cited SaxonF @SaxonF github-actions[bot] @github-actions[bot]

ClickHouse is now a first-class replication destination in Studio, gated behind a private alpha flag and built with client-side validation that blocks insecure and internal URLs.

The big move today is ClickHouse integration [1]. Studio now renders a full configuration form for ClickHouse destinations with URL, user, password, and database fields. The implementation includes client-side validation that rejects any target pointing to loopback addresses, RFC 1918 ranges, link-local ranges, CGNAT blocks, or IPv6 ULA space. This is security by default, not an afterthought. The flag is off by default, so you won't see this in production orgs yet. In parallel, the auth layer shipped support for multiple custom sign-in providers [2]. The UI now renders all configured custom providers on the sign-in page while staying backward compatible with the legacy single-provider setup. Over in go-tpc, error propagation got fixed [3]. TPCC subcommands were exiting with code 0 even on failure, masking preparation errors upstream. That's now corrected. The realtime team squashed a flaky reconnector test [4] that was making local development harder. Small fix, high signal-to-noise on CI runs.

$ 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 July 20, 2026?
ClickHouse is now a first-class replication destination in Studio, gated behind a private alpha flag and built with client-side validation that blocks insecure and internal URLs. In total, 5 commits, 5 pull requests, and 1 releases landed.
Who contributed to Supabase on July 20, 2026?
6 developers shipped this update, including SaxonF, jmqd, Joshen Lim, danielmitterdorfer, github-actions[bot], and Eduardo Gurgel.
What were the notable Supabase updates?
feat(studio): add ClickHouse replication destination, Add support for multiple custom auth providers in custom-content (#48030), and Propagate errors to top-level for TPCC.
♥

$ 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.