RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

  1. Sat 2 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

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

By RepoJournal · Filed · About Supabase

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

FAQ

What changed 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.
What should Supabase teams do about it?
Deploy Supavisor with IPv6 fix if running IPv6-only infrastructure • Update MCP server dependencies to v0.8.2+ for test reliability • Test production branch resync in non-prod Studio instances first
Which Supabase repositories shipped on June 8, 2026?
supabase/supavisor, supabase/mcp, supabase/postgres, supabase/supabase

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.