The Wire · Showcase
STUDIO LOGS GET HUMAN-READABLE PARSING, DATA API SCHEMA CLEANUP LANDS
By RepoJournal · Filed · About Supabase
Auth log entries that were rendering as raw JSON strings in your dashboard now display clean, readable messages, while a critical fix lets users remove orphaned schemas crashing their Data API clients.
The studio team shipped a parsing fix [1] that extracts human-readable event messages from auth logs that were previously displayed as stringified JSON objects like {"msg":"user signed in","level":"info"}. In parallel, they landed a schema management fix [2] that detects and displays missing schemas in the Data API settings, preventing silent Postgrest client crashes and letting users unselect broken references. The UI package also got cleaner component exports [3] after removing unnecessary naming aliases from Command components. Meanwhile, the postgres desk bumped pg_net to 0.20.3 [4], picking up two critical fixes: autovacuum will now properly schedule after worker writes thanks to pgstat counter flushing [4], and a worker permission reporting issue got resolved. The realtime layer addressed permission composition bugs [5] where tenant database baseline configurations were missing grants defined in migrations, and pushed a cowboy dependency bump [6] to patch a known CVE.
Action items
- → Test auth logs in your studio instance to confirm message parsing works correctly supabase/supabase [plan]
- → Check Data API settings for any orphaned schemas and clean them up supabase/supabase [plan]
- → Monitor autovacuum behavior on realtime instances after pg_net 0.20.3 deployment supabase/postgres [monitor]
References
- [1] fix(studio): parse auth log event_message JSON for human-readable display DEBUG-111 (#46147) supabase/supabase
- [2] fix: allow users to remove missing schemas from the data API (#46169) supabase/supabase
- [3] chore: remove `_Shadcn_` suffix from `Command` components (#46153) supabase/supabase
- [4] chore: bump to pg_net 0.20.3 ↗ supabase/postgres
- [5] fix: compose tenant db permissions ↗ supabase/realtime
- [6] fix: bump up cowboy ↗ supabase/realtime
FAQ
- What changed in Supabase on May 21, 2026?
- Auth log entries that were rendering as raw JSON strings in your dashboard now display clean, readable messages, while a critical fix lets users remove orphaned schemas crashing their Data API clients.
- What should Supabase teams do about it?
- Test auth logs in your studio instance to confirm message parsing works correctly • Check Data API settings for any orphaned schemas and clean them up • Monitor autovacuum behavior on realtime instances after pg_net 0.20.3 deployment
- Which Supabase repositories shipped on May 21, 2026?
- supabase/supabase, supabase/postgres, supabase/realtime