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-08
stories 105

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

SUPAVISOR HARDENS SECURITY CHECKS, MCP SERVERS SHIP FIXES, POSTGRES VERSIONING SURGE

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

Supavisor moved security scanning to PR branches and fixed critical IPv6 detection, while three MCP packages shipped coordinated updates after a repository transfer.

Supavisor landed a critical security workflow fix that stops pushing dependencies to GitHub for non-main branches, cutting noise from false-positive CVE alerts [1]. In the same system, IPv6-only database hosts now work out of the box without manual configuration [2], matching tenant DB behavior. The connection pooler also eliminated a race condition in tenant metrics tests [3], tightening test reliability across the stack.

MCP completed a coordinated release across three packages [4] [5] [6], fixing edge function test typos and updating repository URLs after the supabase/mcp transfer. All three packages shipped simultaneously with identical repository fixes.

Postgres released five new build variants [7] [8] [9] [10] [11] spanning versions 15 and 17 with pgcron support across architectures. Studio shipped feature work enabling production branch resyncs [12], improved self-hosted storage testing with hash validation [13], and fixed a critical bug where sidebar filters in unified logs weren't actually filtering [15]. A new Create Index form refactor aligns database tooling with Studio patterns [14].

Action items

References

  1. [1] fix: run security check from pull request branch (#1028) ↗ supabase/supavisor
  2. [2] fix: auto-detect ipv6 from metadata db hostname (#1027) ↗ supabase/supavisor
  3. [3] test: fix race in tenant metrics aggregation tests (#1026) ↗ supabase/supavisor
  4. [4] mcp-server-supabase: v0.8.2 ↗ supabase/mcp
  5. [5] mcp-server-postgrest: v0.1.1 ↗ supabase/mcp
  6. [6] mcp-utils: v0.5.1 ↗ supabase/mcp
  7. [7] 17.6.0.089-orioledb-pgcron-6-x86 ↗ supabase/postgres
  8. [8] 17.6.1.132-pgcron-6-x86 ↗ supabase/postgres
  9. [9] 15.14.1.132-pgcron-6-x86 ↗ supabase/postgres
  10. [10] 15.14.1.132-pgcron-2 ↗ supabase/postgres
  11. [11] 17.6.1.132-pgcron-2 ↗ supabase/postgres
  12. [12] feat: allow to resync production branches (#46723) ↗ supabase/supabase
  13. [13] chore(self-hosted): add test for tus ↗ supabase/supabase
  14. [14] chore: create index form ↗ supabase/supabase
  15. [15] fix(unified-logs): apply sidebar facet filters on click ↗ supabase/supabase

Quick answers

What shipped in Supabase on June 8, 2026?
Supavisor moved security scanning to PR branches and fixed critical IPv6 detection, while three MCP packages shipped coordinated updates after a repository transfer. In total, 46 commits, 46 pull requests, and 13 releases landed.
Who contributed to Supabase on June 8, 2026?
3 developers shipped this update, including aantti, ChloeGarciaMillerand, and jordienr.
What were the notable Supabase updates?
fix: run security check from pull request branch (#1028), fix: auto-detect ipv6 from metadata db hostname (#1027), and test: fix race in tenant metrics aggregation tests (#1026).