RepoJournal
Supabase @supabase
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-08-16
stories 8
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

SUPABASE CLI FIXES MEMORY BLOWUP ON LARGE DB DUMPS

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

7ttp jgoux
2 people shipped this
7ttp @7ttp 4 cited jgoux @jgoux 1 cited

The CLI was buffering entire piped outputs in memory instead of respecting backpressure, turning a routine `supabase db dump` into an OOM killer on large databases.

The root cause was straightforward and brutal: stdout writes ignored their return value, so Node had no signal to pause when the reader slowed down [1]. Large payloads piled up in the heap. The fix routes output through a proper Stdio sink that waits for drain events and handles stream errors, a change that's already shipping [2]. In the same sweep, the CLI now correctly fails `supabase test db` when zero tests execute [3], closing a gap where typo'd paths or empty directories would report success because pg_prove exits 0 even on NOTESTS verdicts. The TAP summary now gets watched for that specific result, and failures name the paths that were searched [4]. A third fix settles managed identity recovery races safely, preserving Git config and marker semantics across interrupted branch operations [5].

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

the week in review CLI 2.120.0 adds persisted logs and OTel traces the month in review MCP v0.12.0 groups advisor lints, adds cost elicitation
Full archive → Weekly reviews →

Quick answers

What shipped in Supabase on August 16, 2026?
The CLI was buffering entire piped outputs in memory instead of respecting backpressure, turning a routine `supabase db dump` into an OOM killer on large databases. In total, 3 commits, 3 pull requests, and 2 releases landed.
Who contributed to Supabase on August 16, 2026?
2 developers shipped this update, including 7ttp and jgoux.
What were the notable Supabase updates?
fix(cli): stop buffering piped output, fix(cli): stop buffering piped output (#6212), and fix(cli): fail test db when no tests ran (CLI-2194).
♥

$ log @supabase --recent

Self-hosted stack bumps realtime and storage, Studio remembers your chart range 72 shipped Realtime 2.144.0 patches a decimal CVE; realtime-csharp adds paged storage listing 151 shipped MCP server 0.14.0 adds health advisors, Supabase CLI routes every Management API call through the typed client 123 shipped Scoped OAuth reconsent in Studio, MCP drops double cost prompts 139 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training verl rejects conflicting vLLM engine_kwargs, open-instruct adds MILES OPD behind a Megatron learner Interpretability nnsight 0.8.0 cuts import time from 7.6s to 1.6s

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

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