What shipped in Supabase on August 19, 2026?

If you run schema diffing or supabase test db in CI, this release is about to change what those commands do. In total, 28 commits, 31 pull requests, and 20 releases landed.

Who contributed to Supabase on August 19, 2026?

8 developers shipped this update, including github-actions[bot], Vaibhav, Andrew Valleteau, Cemal Kılıç, charislam, joshenlim, barryroodt, and iambriccardo.

What were the notable Supabase updates?

v2.115.0, fix(cli): surface crashed migra diffs (CLI-2204) (#6240), and fix(cli): classify batch connection failures as connect errors (#6234).

@supabase

The open-source Firebase alternative powering thousands of startups

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

SUPABASE CLI v2.115.0 BREAKS YOUR CI

By RepoJournal · Filed 06:58 UTC on August 19, 2026 · About Supabase

8 people shipped this

github-actions[bot] @github-actions[bot] 6 cited

Andrew Valleteau @avallete 2 cited

Vaibhav @7ttp 1 cited

barryroodt @barryroodt 1 cited

iambriccardo @iambriccardo 1 cited

Cemal Kılıç @cemalkilic

charislam @charislam

joshenlim @joshenlim

If you run schema diffing or supabase test db in CI, this release is about to change what those commands do.

Supabase CLI v2.115.0 [1] ships breaking changes that hit two common CI workflows: `db diff`, `db pull`, and declarative schema now default to the bundled pg-delta engine, and `supabase test db` now fails when it finds zero tests. The pg-delta switch is the big one, because it affects every diff-based command, says the release notes: "Schema diffing defaults to the bundled pg-delta engine" [1]. Hardening landed alongside it: a fix [2] stops `db diff --use-migra` from silently printing "No schema changes found" and exiting 0 when the migra template crashes, plus another [3] that reclassifies batch connection failures as connect errors instead of exec failures, and a stack deflake [4] that kills a family of intermittent test failures. Meanwhile, the evals team made it possible to test unpublished `mcp-server-supabase` changes locally via `SUPABASE_MCP_SERVER_PATH` [5], and the ETL pipeline reworked how schema diffs are applied, matching columns by PostgreSQL `attnum` so renames keep identity [6]. Postgres releases are routine this cycle: PostgREST bumped to v14.17 in the CLI build [7], plus the usual orioledb and point releases [8][9][10][11].

Action items

→ Read the v2.115.0 changelog and adapt CI scripts before next deploy supabase/cli [immediate]
→ Set SUPABASE_MCP_SERVER_PATH in evals workspace to test local MCP changes supabase/evals [plan]
→ Review ETL diff rework for attnum-based column matching supabase/etl [monitor]

References

[1] v2.115.0 ↗ supabase/cli
[2] fix(cli): surface crashed migra diffs (CLI-2204) (#6240) supabase/cli
[3] fix(cli): classify batch connection failures as connect errors (#6234) supabase/cli
[4] fix(stack): deflake service-state settling and control endpoint acquisition (#6245) supabase/cli
[5] feat(core): launch a local mcp build via SUPABASE_MCP_SERVER_PATH ↗ supabase/evals
[6] fix(ddl): Rework how schema diffs are applied ↗ supabase/etl
[7] v17.6.1.165-cli ↗ supabase/postgres
[8] 17.9.0.018-orioledb-x86 ↗ supabase/postgres
[9] 15.14.1.165 ↗ supabase/postgres
[10] 17.6.1.165 ↗ supabase/postgres
[11] 17.9.0.018-orioledb ↗ supabase/postgres

Quick answers

What shipped in Supabase on August 19, 2026?: If you run schema diffing or supabase test db in CI, this release is about to change what those commands do. In total, 28 commits, 31 pull requests, and 20 releases landed.
Who contributed to Supabase on August 19, 2026?: 8 developers shipped this update, including github-actions[bot], Vaibhav, Andrew Valleteau, Cemal Kılıç, charislam, joshenlim, barryroodt, and iambriccardo.
What were the notable Supabase updates?: v2.115.0, fix(cli): surface crashed migra diffs (CLI-2204) (#6240), and fix(cli): classify batch connection failures as connect errors (#6234).

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

@supabase Aug 18

SUPABASE HARDENS CORS AND SHIPS PROMPT-INJECTION EVALS

A config hardening for self-hosted envoy plus four new security evals signal Supabase is closing attack surfaces on both the infrastructure and AI agent fronts.

javascript 85 shipped

@supabase Aug 17

SUPABASE STUDIO TIGHTENS PRIVATELINK UX ACROSS FOUR COMMITS

Four linked PRs ship clarity to PrivateLink configuration and MFA backup flows, replacing ambiguous copy with resource IDs and clearer field ordering.

javascript 24 shipped

@supabase Aug 16

SUPABASE CLI FIXES MEMORY BLOWUP ON LARGE DB DUMPS

The CLI was buffering entire piped outputs in memory instead of respecting backpressure, turning a routine `supabase db dump` into an OOM killer on large databases.

javascript 8 shipped

Elsewhere on the wire

AI Agents Aug 20

LangChain ships core 1.6.0 with a security warning tucked inside

LangChain's newest core release fixes a tool-injection bug, but the fix itself widens the path for arbitrary code execution.

ai-agents 95 shipped

Local LLMs Aug 20

OLLAMA FIXES DEADLOCK THAT HUNG CHAT AND GENERATE

A mid-stream parser error in Ollama's server silently wedged chat and generate requests, leaking goroutines and hanging retries until a fix landed overnight.

+14

llms 268 shipped

@CachyOS Aug 20

LINUX-CACHYOS SHIPS 7.2.0-1

CachyOS's custom kernel just advanced to 7.2.0-1, and the sched-ext toolchain is moving in lockstep.

infra 55 shipped

Elixir & Phoenix Aug 20

LIVE VIEW HOOKS GET THE ELOQUENT TREATMENT

Phoenix Live View is shipping a passel of hook and JS-client fixes today, headlined by new beforeUpdate arguments that hand you more control over a hook's lifespan.