111 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-09-02
stories 71

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Shared DuckDB pooling, group advisor lints, realtime v2.133.0

By RepoJournal · Filed · About Supabase

DuckDB connections now share a single instance with multiple connections, advisor output groups lints to cut response bloat, and realtime v2.133.0 ships across platforms.

supabase/etl now reuses one DuckDB instance with a pool of connections instead of spawning separate instances per connection, cutting overhead and adding deferred durability in the SYNC phase plus a deadlock fix that also recreates the pool after maintenance [1]. This is an improvement, not a behavior change for callers. The MCP server's `get_advisors` response groups lints so repeated findings no longer repeat the same `title`, `description`, and `remediation` strings hundreds of times, shrinking the response payload [2]. supabase-js v2.113.0 adds realtime support to wait for pg changes, building on the canary released a day earlier [3]. slim-services shipped realtime v2.133.0 for linux/amd64, linux/arm64, and darwin/arm64 with a multi-platform Docker image [4]. A BEAM fix preserves explicit distribution overrides like `none` in Mix release env files, preventing native launches from detaching host `epmd` daemons [5]. UI library adds a backend-only MCP server block that exposes user-scoped MCP tools via an Edge Function [6]. Docs updates correct the API key rotation steps and restructure the API keys guide to separate context, procedure, and reference material [7][8].

Action items

References

  1. [1] refactor(ducklake): use shared duckdb instances with multiple connections ↗ supabase/etl
  2. [2] feat: group lints in `get_advisors` response ↗ supabase/mcp
  3. [3] v2.113.0 ↗ supabase/supabase-js
  4. [4] realtime v2.133.0 ↗ supabase/slim-services
  5. [5] fix: preserve native BEAM distribution overrides ↗ supabase/slim-services
  6. [6] feat(ui-library): add MCP server block (#49573) ↗ supabase/supabase
  7. [7] docs: add the missing API key decision information (#49799) ↗ supabase/supabase
  8. [8] docs: restructure the API keys guide by information type (#49796) ↗ supabase/supabase

Quick answers

What shipped in Supabase on September 2, 2026?
DuckDB connections now share a single instance with multiple connections, advisor output groups lints to cut response bloat, and realtime v2.133.0 ships across platforms. In total, 34 commits, 34 pull requests, and 3 releases landed.
Who contributed to Supabase on September 2, 2026?
10 developers shipped this update, including bnjjj, Gildas Garcia, Saxon Fletcher, Miranda Limonczenko, Matt Rossman, supabase-releaser, supabase-releaser[bot], and github-actions[bot], and 2 more.
What were the notable Supabase updates?
refactor(ducklake): use shared duckdb instances with multiple connections, feat: group lints in `get_advisors` response, and v2.113.0.