The Wire · Showcase
DOCS CONTENT API NOW PLUGGABLE, RLS LEAK PATCHED IN STUDIO
By RepoJournal · Filed · About Supabase
11 people shipped this
Francesco Sansalvadore
@fsansalvadore
2 cited
jmqd
@jmqd
2 cited
farazdagi
@farazdagi
2 cited
barryroodt
@barryroodt
1 cited
Alaister Young
@alaister
1 cited
jordienr
@jordienr
1 cited
iambriccardo
@iambriccardo
1 cited
supabase-releaser
@supabase-releaser
supabase-releaser[bot]
@supabase-releaser[bot]
github-actions[bot]
@github-actions[bot]
david birdsong
@davidbirdsong
The MCP server can point at alternative GraphQL endpoints for docs testing, while a critical fix stops Studio from leaking RLS-protected values during cell loads.
The MCP server gains pluggable docs content infrastructure with a new `--content-api-url` flag and `SUPABASE_CONTENT_API_URL` env var [1]. This wires the evals harness so docs changes can be tested end to end before shipping: build a local content index, point `search_docs` at it, and run assertions. Behavior without either flag or env var remains unchanged, defaulting to the hosted GraphQL endpoint.
Studio shipped a critical RLS bypass fix [2]. When loading truncated cell values from inline grid or row side-panel editors, the fetch ran with full DB privileges instead of the role selected in View as role, leaking values RLS would deny. The same `roleImpersonationState` fix applied to row copy/export in prior work now covers all 4 truncated-cell code paths.
The www changelog system shifted from direct YAML parsing to a structured sync from the private changelog repo [3], with a follow-up security patch [4] that strips private frontmatter fields like `internal:` and `reviewers:` before client serialization. Logs Explorer docs are now ClickHouse-focused [5], documenting the single `logs` table tagged by `source` with nested `log_attributes` since June 2026, removing obsolete BigQuery cross join guidance.
ETL landed three production fixes: slot recreation now proceeds with warnings instead of failing when tables desync [6], array dimension prefix parsing corrects Postgres output like `[0:1]={7,8}` [7], and stale Snowflake schema snapshots skip reverse DDL during replay [8]. Pipeline startup now rejects double-start calls before side effects [9], and daily fuzz runs accumulate corpus coverage across runs [10].
One email a day. Unsubscribe in one click.
Keep up with Supabase in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Deploy Studio role impersonation fix to production supabase/supabase [immediate]
- → Review changelog frontmatter exposure in your docs builds supabase/supabase [plan]
- → Test MCP docs content API override if running local evals supabase/mcp [monitor]
- → Pull latest Postgres 17.6.1.154 and 15.14.1.154 builds supabase/postgres [plan]
References
- [1] feat: add --content-api-url flag and SUPABASE_CONTENT_API_URL env var ↗ supabase/mcp
- [2] [FE-3544] fix(studio): role impersonation for truncated cell loads ↗ supabase/supabase
- [3] feat(www): new changelog sync ↗ supabase/supabase
- [4] fix(www): changelog frontmatter (#48249) supabase/supabase
- [5] docs(telemetry): make the Logs Explorer docs ClickHouse-focused ↗ supabase/supabase
- [6] fix(core): Improve handling of apply slot recreation ↗ supabase/etl
- [7] Fix array dimension prefix parsing and add codec fuzz targets ↗ supabase/etl
- [8] fix(snowflake): skip stale schema snapshots during replay ↗ supabase/etl
- [9] fix(core): prevent starting a pipeline twice ↗ supabase/etl
- [10] ci: Add a daily scheduled fuzz workflow ↗ supabase/etl
