What shipped in Supabase on August 24, 2026?

Supabase just made it impossible to run a destructive notebook query by accident. In total, 5 commits and 5 pull requests landed.

Who contributed to Supabase on August 24, 2026?

5 developers shipped this update, including Joshen Lim, claude[bot], dnywh, supabase-evals-releaser, and supabase-evals-releaser[bot].

What were the notable Supabase updates?

Add confirmation modal when running notebook if notebook contains query cells that aren't read only (#49376), Add confirmation modal when running notebook if notebook contains query cells that aren't read only, and Joshenlim/fe 4221 explorer tab behaviours to mimic sql editor.

@supabase

The open-source Firebase alternative powering thousands of startups

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

SUPABASE TURNS NOTEBOOK RUNS INTO A MUTATION SAFETY NET

By RepoJournal · Filed 06:57 UTC on August 24, 2026 · About Supabase

5 people shipped this

Joshen Lim @joshenlim 3 cited

claude[bot] @claude[bot] 1 cited

dnywh @dnywh 1 cited

supabase-evals-releaser @supabase-evals-releaser 1 cited

supabase-evals-releaser[bot] @supabase-evals-releaser[bot] 1 cited

Supabase just made it impossible to run a destructive notebook query by accident.

Supabase shipped a confirmation modal that intercepts "run notebook" when any query cell mutates data, with an escape hatch to run only the read-only cells [1]. The same PR landed under a second number, so the change is effectively pinned twice [2]. Meanwhile, explorer tabs now behave exactly like the SQL Editor: they start as preview tabs, become permanent once you interact, and notebooks with unsaved changes show an orange dot [3]. On the cleanup front, the studio dropped the dead unified logs banner telemetry and its storage key [4], and docs admonition structure is getting tidied to fix awkward callout layouts [5]. Over in evals, the automated pipeline refreshed `eval-results.json` [6][7], keeping the web app's eval numbers current. Activity was light: 5 commits and 5 PRs across the two repos. The modal is the story of the day: it's the kind of guardrail that prevents a very bad Monday.

Action items

→ Pull #49376 into your Supabase branch before anyone else runs a destructive notebook supabase/supabase [immediate]
→ Review the explorer tab behavior change in #49386 and update any UI tests supabase/supabase [plan]
→ Verify the eval results refresh in supabase/evals is picked up by your web build supabase/evals [monitor]

References

[1] Add confirmation modal when running notebook if notebook contains query cells that aren't read only (#49376) supabase/supabase
[2] Add confirmation modal when running notebook if notebook contains query cells that aren't read only ↗ supabase/supabase
[3] Joshenlim/fe 4221 explorer tab behaviours to mimic sql editor ↗ supabase/supabase
[4] chore(studio): remove dead unified logs banner telemetry and storage key (#49454) supabase/supabase
[5] clean up docs admonition structure ↗ supabase/supabase
[6] chore: refresh eval results ↗ supabase/evals
[7] chore: refresh eval results (#227) supabase/evals

Quick answers

What shipped in Supabase on August 24, 2026?: Supabase just made it impossible to run a destructive notebook query by accident. In total, 5 commits and 5 pull requests landed.
Who contributed to Supabase on August 24, 2026?: 5 developers shipped this update, including Joshen Lim, claude[bot], dnywh, supabase-evals-releaser, and supabase-evals-releaser[bot].
What were the notable Supabase updates?: Add confirmation modal when running notebook if notebook contains query cells that aren't read only (#49376), Add confirmation modal when running notebook if notebook contains query cells that aren't read only, and Joshenlim/fe 4221 explorer tab behaviours to mimic sql editor.

Supabase Guards QueryEditor Against Destructive Queries

Supabase's QueryEditor now enforces SQL editor safety checks, blocking destructive operations without a WHERE clause.

javascript 6 shipped

@supabase Aug 22

JUDGE UPGRADE: evals now reasons at medium effort

Supabase's eval judge is getting smarter, but the RLS guide fix is the one that will keep your docs green.

javascript 92 shipped

@supabase Aug 21

MCP SERVERS MOVE TO SDK V2

Supabase's MCP packages cut over to the v2 wire protocol today, and if you consume them, the next upgrade is not optional.

+11

javascript 126 shipped

@supabase Aug 20

ROW LEVEL SECURITY DOCS GET A REWRITE

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

javascript 56 shipped

Elsewhere on the wire

AI Agents Aug 24

CLINE SHIPS V4.1.15 AS TELEMETRY BUGS SURFACE ACROSS THE AGENT STACK

Cline's long-awaited auto-approve fix landed overnight, but it's the telemetry drop in 4.1.11 that should have you checking your session metrics.

ai-agents 44 shipped

Local LLMs Aug 24

VLLM'S P2P WEIGHT SYNC CUTS RL MOE TRANSFER COSTS

Forget all-gathering experts during RL rollout: vLLM's new sharded_rdt backend lets each worker pull only the slice it needs, turning a total_bytes transfer into a total_bytes divided by num_workers one.