RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

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

The Wire · Showcase

STUDIO LOCKS DOWN SHARED REPORTS, CLI GATES EXPERIMENTAL COMMANDS, REALTIME PATCHES MIGRATION GAPS

By RepoJournal · Filed · About Supabase

Supabase Studio now forces private SQL snippets public before adding them to team reports, closing a hole where collaborators saw broken states.

The Studio team shipped a critical fix [1] that prevents the 'SQL snippet not found' error when teammates view reports containing private snippets. When you pick a private snippet for a report, the system now confirms and shares it with the project before adding it, while drag-and-drop additions get the same treatment [1]. The fix also cleaned up type safety in the report model [2], and the team completed a design refresh for the Vercel integration flow [3] alongside removing deprecated Shadcn tab component naming across the UI [4]. Over on CLI, the team discovered seven commands (postgres-config, ssl-enforcement, network-bans) were running without the required `--experimental` flag gate [5], and also fixed ordering so invalid project refs surface before IP validation errors [6]. Realtime v2.112.6 shipped with migrations that handle missing schema tables and missing admin roles on older PG versions [7] [9], plus fixed execution permissions on the check_equality_op function [8].

Action items

References

  1. [1] feat(studio): share report snippets with the team when added to homepage report FE-3800 ↗ supabase/supabase
  2. [2] fix: remove any from report snippet model (#47644) supabase/supabase
  3. [3] Vercel install layout ↗ supabase/supabase
  4. [4] chore: remove `_Shadcn_` suffix from `ui` tabs components (#47628) supabase/supabase
  5. [5] fix(cli): wire --experimental gate into 7 ungated native leaves (#5766) supabase/cli
  6. [6] fix(cli): resolve network-bans project ref before validating --db-unban-ip (#5769) supabase/cli
  7. [7] fix(dashboard): tenants migrations edge cases ↗ supabase/realtime
  8. [8] fix: grant exec on `realtime.check_equality_op/5` ↗ supabase/realtime
  9. [9] v2.112.6 ↗ supabase/realtime

FAQ

What changed in Supabase on July 7, 2026?
Supabase Studio now forces private SQL snippets public before adding them to team reports, closing a hole where collaborators saw broken states.
What should Supabase teams do about it?
Update Studio to latest build to prevent broken shared reports • Upgrade Realtime to v2.112.6 if running self-hosted with PG15 or older • Review CLI commands using --experimental flag to ensure they're now gated correctly
Which Supabase repositories shipped on July 7, 2026?
supabase/supabase, supabase/cli, supabase/realtime

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.