RepoJournal
Supabase @supabase
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-08-20
stories 56
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

ROW LEVEL SECURITY DOCS GET A REWRITE

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

Miranda Limonczenko kanad claude[bot] Saxon Fletcher
4 people shipped this
Miranda Limonczenko @czenko 2 cited kanad @kanadgupta 1 cited claude[bot] @claude[bot] 1 cited Saxon Fletcher @SaxonF 1 cited

Supabase restructured its RLS documentation overnight, splitting the guide into clear sections so developers can find what they need without wading through reference material.

Miranda Limonczenko reorganized the RLS guide into three sections by information type, separating understanding, securing, and reference [1]. The old guide "alternated between context, procedure, and reference on almost every heading," forcing readers to skip through four sections to write a policy [1]. Performance tuning now lives in its own guide, trimming 225 lines of benchmark tables from the main page, and addressing the core question of whether RLS is actually your bottleneck [2]. Beyond docs, Supabase added a migration to collect product feedback from the CLI and MCP server, with token-based deletion support [3]. The Studio team also fixed an unguarded read on the OAuth authorize pages, closing a potential null reference crash [4], and improved the assistant's SQL rendering with AssistantQueryCell [5].

Action items

References

  1. [1] docs(database): restructure the RLS guide by information type (#49017) supabase/supabase ↗
  2. [2] docs(database): split RLS tuning into its own guide (#49016) supabase/supabase ↗
  3. [3] feat: table for collecting interfaces feedback (#48420) supabase/supabase ↗
  4. [4] fix(studio): guard unguarded requester.name reads on the OAuth authorize and apps pages (#49267) supabase/supabase ↗
  5. [5] feat(studio): render assistant SQL with AssistantQueryCell (#49170) supabase/supabase ↗

$ ls supabase/reviews/ # the step-back reads

the week in review CLI 2.120.0 adds persisted logs and OTel traces the month in review MCP v0.12.0 groups advisor lints, adds cost elicitation
Full archive → Weekly reviews →

Quick answers

What shipped in Supabase on August 20, 2026?
Supabase restructured its RLS documentation overnight, splitting the guide into clear sections so developers can find what they need without wading through reference material. In total, 28 commits and 28 pull requests landed.
Who contributed to Supabase on August 20, 2026?
4 developers shipped this update, including Miranda Limonczenko, kanad, claude[bot], and Saxon Fletcher.
What were the notable Supabase updates?
docs(database): restructure the RLS guide by information type (#49017), docs(database): split RLS tuning into its own guide (#49016), and feat: table for collecting interfaces feedback (#48420).
♥

$ log @supabase --recent

Self-hosted stack bumps realtime and storage, Studio remembers your chart range 72 shipped Realtime 2.144.0 patches a decimal CVE; realtime-csharp adds paged storage listing 151 shipped MCP server 0.14.0 adds health advisors, Supabase CLI routes every Management API call through the typed client 123 shipped Scoped OAuth reconsent in Studio, MCP drops double cost prompts 139 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training verl rejects conflicting vLLM engine_kwargs, open-instruct adds MILES OPD behind a Megatron learner Interpretability nnsight 0.8.0 cuts import time from 7.6s to 1.6s

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.