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

STUDIO PARSER FIX LANDS AS POSTGRES RCS ROLL AND REALTIME HARDENS MIGRATIONS

By RepoJournal · Filed · About Supabase

The SQL Editor's RLS detection was silently failing on ALTER TABLE IF EXISTS queries—that's fixed [ref:1], while five Postgres release candidates [ref:6][ref:7][ref:8][ref:9][ref:10] and Realtime's migration safety push [ref:15] move through the pipeline.

A parser regex in the Studio was capturing IF as a table name when users wrote ALTER TABLE IF EXISTS, causing RLS events to never match their CREATE TABLE statements—the fix now accepts Postgres's optional IF EXISTS and ONLY modifiers [1]. The Studio also shipped keyboard shortcuts across all Database listing pages , refactored publications to use the PageLayout component , and cleaned up legacy audit log query params . Documentation is migrating from anon/service_role naming to publishable/secret keys [11] to stay consistent with SDK changes. On the infrastructure side, Supabase Postgres released four rc builds across versions 15 and 17 [2][3][4][6], while Realtime v2.90.0 [7] exposed tenant migration observability metrics and added error granularity to policy failures [8][9]. The team is also making migrations more resilient [10] as step one of a broader hardening effort.

Action items

References

  1. [1] [FE-3134] fix(studio): handle ALTER TABLE IF EXISTS in RLS detection (#45493) supabase/supabase
  2. [2] 17.6.0.071-rc4 ↗ supabase/postgres
  3. [3] 17.6.1.114-rc4 ↗ supabase/postgres
  4. [4] 15.14.1.114-rc4 ↗ supabase/postgres
  5. [5] 15.14.1.114-rc4-x86 ↗ supabase/postgres
  6. [6] 17.6.0.071-rc4-x86 ↗ supabase/postgres
  7. [7] v2.90.0 ↗ supabase/realtime
  8. [8] fix: add granularity to unable to set policies errors ↗ supabase/realtime
  9. [9] feat(observability): expose tenant migration metrics ↗ supabase/realtime
  10. [10] fix: unblock tenants and make migrations safer ↗ supabase/realtime
  11. [11] docs: prefer publishable/secret key naming in SDK specs ↗ supabase/supabase

FAQ

What changed in Supabase on May 5, 2026?
The SQL Editor's RLS detection was silently failing on ALTER TABLE IF EXISTS queries—that's fixed , while five Postgres release candidates and Realtime's migration safety push move through the pipeline.
What should Supabase teams do about it?
Test your ALTER TABLE IF EXISTS queries in Studio—the RLS detection now works correctly • Review Realtime v2.90.0 for improved migration observability if you run self-hosted • Update SDK spec references from anon/service_role to publishable/secret in your docs
Which Supabase repositories shipped on May 5, 2026?
supabase/supabase, supabase/postgres, 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.