151 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-05-05
stories 113

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

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

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

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

Quick answers

What shipped in Supabase on May 5, 2026?
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. In total, 52 commits, 49 pull requests, and 12 releases landed.
Who contributed to Supabase on May 5, 2026?
3 developers shipped this update, including filipecabaco, leandrocp, and mandarini.
What were the notable Supabase updates?
[FE-3134] fix(studio): handle ALTER TABLE IF EXISTS in RLS detection (#45493), 17.6.0.071-rc4, and 17.6.1.114-rc4.