151 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-10-06
stories 174

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

supautils builds against PG19beta1, www stops cross-zone link prefetch

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

Two infrastructure fixes and one large docs restructuring land today: supautils is now PG19beta1-ready, www kills the RSC prefetches that made up roughly 95% of its 404s, and the Database functions guide gets split and corrected.

chore: PG19beta1 compatibility and CI supabase/supautils

by mkaruza

supautils now compiles with -std=gnu11, fixes the timezone check hook for the PG 19 GUC struct layout, and runs PG 19 in CI. pg_tle still has no PG 19 release, so the extension builds it from a pinned main commit, which is the piece to watch if you build against Postgres 19 betas.

fix(www): stop cross-zone link prefetch (#51066) supabase/supabase

by Pamela Chia

About 95% of the 404s served on supabase.com were App Router RSC prefetches (_rsc=) fired at paths another zone serves, including /docs, /dashboard, /library and the footer's humans.txt, lawyers.txt and security.txt links. Next.js can't prefetch or client-navigate across multi-zone boundaries, so every www <Link> pointing at another zone is now a plain <a>, enforced by a new lint rule.

feat: align agent traces with Braintrust's span spec supabase/evals

by mattrossman

Each eval run's trace now follows the trace shape in Braintrust's eval span spec, with span naming mirroring their Claude Code plugin. Traces that previously ended at the result file's mtime now line up with the spec's expected spans.

fix(core): pass only MCP arguments as Codex tool-call input supabase/evals

by barryroodt

The Codex parser was putting the entire MCP item, tool result included, into tool_call.input, so judges using serializeTranscript with includeToolCallInputs: true received full MCP outputs (search_docs results up to ~150k chars) for Codex runs only. Input is now just the call arguments, matching the Claude Code, Grok and OpenCode parsers, with the result left on the tool result.

docs(database): connect security definer to the default execute grant (#50817) supabase/supabase

by Miranda Limonczenko

The Database functions guide gains content it never had on how security definer mode connects to the default execute grant, closing out a four-part docs stack. Companion changes in the same stack regroup the guide's eight top-level headings into groups of 5 plus or minus 1, fix a planets table whose serial sequence stays at 0 because the seed sets ids explicitly, and turn www links into another...

Quick answers

What shipped in Supabase on October 6, 2026?
Two infrastructure fixes and one large docs restructuring land today: supautils is now PG19beta1-ready, www kills the RSC prefetches that made up roughly 95% of its 404s, and the Database functions guide gets split and corrected. In total, 84 commits, 85 pull requests, and 5 releases landed.
Who contributed to Supabase on October 6, 2026?
8 developers shipped this update, including mkaruza, supabase-evals-releaser, Rodriguespn, mattrossman, barryroodt, Miranda Limonczenko, Pamela Chia, and 7ttp.
What were the notable Supabase updates?
chore: PG19beta1 compatibility and CI, fix(www): stop cross-zone link prefetch (#51066), and feat: align agent traces with Braintrust's span spec.