Who contributed to Supabase on August 4, 2026?

12 developers shipped this update, including Alaister Young, Nik Richers, Stephen Morgan, Joshen Lim, avallete, supabase-releaser[bot], supabase-releaser, and 7ttp, and 4 more.

What were the notable Supabase updates?

fix(studio): redirect to feature preview route after enabling (#48637), Bring database connections to feature preview (#48638), and fix(pg-topo): slice statements by byte offsets so non-ASCII SQL is carried verbatim.

@supabase

The open-source Firebase alternative powering thousands of startups

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

STUDIO REDIRECTS FIXED, DATABASE CONNECTIONS ENTER PREVIEW, PG-TOOLBELT HANDLES UTF-8

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

12 people shipped this

supabase-releaser[bot] @supabase-releaser[bot] 2 cited

Alaister Young @alaister 1 cited

Nik Richers @nrichers 1 cited

Stephen Morgan @doublethink 1 cited

Joshen Lim @joshenlim 1 cited

avallete @avallete 1 cited

7ttp @7ttp 1 cited

realtime-release-bot[bot] @realtime-release-bot[bot] 1 cited

edgurgel @edgurgel 1 cited

supabase-releaser @supabase-releaser

dependabot @dependabot

leandrocp @leandrocp

Feature preview navigation now works reliably after a nuqs timing bug fix, while database connections move into preview testing across both hosted and self-hosted deployments.

Supabase studio had a routing bug where enabling a feature preview with a dedicated page (like Column-level privileges) would close the modal but fail to navigate to that feature [1]. The issue stemmed from nuqs capturing the pathname before a router.push call and flushing to that stale route, reverting the redirect. That's fixed. Separately, Database Connections now enters feature preview on both hosted and self-hosted instances [2], letting teams test the new connection management system before full rollout. On the pg-toolbelt side, pgdelta declarative apply was mangling non-ASCII SQL comments and policies, rewriting valid `COMMENT ON TRIGGER tr ON public.t` statements into invalid dotted syntax because byte offsets from libpg_query were being applied to UTF-16 string indices [3]. The fix properly slices statements by UTF-8 byte offsets, carrying non-ASCII text verbatim [4]. Documentation expanded with GDPR, ISO 27001, and DDoS coverage guides [5], while PrivateLink docs received security and routing clarifications [6]. JavaScript SDK v2.112.0 landed with OpenTelemetry tracing now opt-in via /tracing subpath, plus a critical auth fix that now preserves server error messages on 5xx failures instead of returning empty JSON [7] [8]. Realtime bumped to v2.123.0 with Erlang OTP and Elixir updates [9], plus improved rebalance logging for cluster member visibility [10].

Action items

→ Update supabase-js to v2.112.0 for auth error message preservation and tracing changes supabase/supabase-js [plan]
→ Test Database Connections feature preview in your environment before full adoption supabase/supabase [monitor]
→ If using pg-toolbelt for schema migrations with non-ASCII content, upgrade to pg-topo@1.0.0-alpha.5 supabase/pg-toolbelt [immediate]

References

[1] fix(studio): redirect to feature preview route after enabling (#48637) supabase/supabase
[2] Bring database connections to feature preview (#48638) supabase/supabase
[3] fix(pg-topo): slice statements by byte offsets so non-ASCII SQL is carried verbatim ↗ supabase/pg-toolbelt
[4] @supabase/pg-topo@1.0.0-alpha.5 ↗ supabase/pg-toolbelt
[5] docs(security): add GDPR, ISO 27001, and DDoS coverage to security guide (#48449) supabase/supabase
[6] fix: cleanup privatelink documentation (#48466) supabase/supabase
[7] v2.112.0 ↗ supabase/supabase-js
[8] fix(auth): preserve 5xx error message (#2587) supabase/supabase-js
[9] v2.123.0 ↗ supabase/realtime
[10] fix: nicer rebalance logs (#2068) supabase/realtime

Quick answers

What shipped in Supabase on August 4, 2026?: Feature preview navigation now works reliably after a nuqs timing bug fix, while database connections move into preview testing across both hosted and self-hosted deployments. In total, 37 commits, 34 pull requests, and 8 releases landed.
Who contributed to Supabase on August 4, 2026?: 12 developers shipped this update, including Alaister Young, Nik Richers, Stephen Morgan, Joshen Lim, avallete, supabase-releaser[bot], supabase-releaser, and 7ttp, and 4 more.
What were the notable Supabase updates?: fix(studio): redirect to feature preview route after enabling (#48637), Bring database connections to feature preview (#48638), and fix(pg-topo): slice statements by byte offsets so non-ASCII SQL is carried verbatim.

POSTGRES CHANGES NOW FILTER AND SELECT COLUMNS, CLI HARDENS SERVICE LIFECYCLE

Supabase shipped Enhancements for Postgres Changes with AND filter composition and column selection, while the CLI consolidated lazy-stack v2 with hardened OS primitives for artifact management.

javascript 81 shipped

@supabase Aug 5

CLI STABILIZES, STUDIO SHIPS MANUAL SAVES AND PRIVATELINK READ REPLICAS

Supabase cut flaky tests across the stack while rolling out editor defaults and networking features that users have been waiting for.

javascript 82 shipped

@supabase Aug 3

STUDIO SHIPPING SAFETY RAILS AS REALTIME HITS 2.122.0

Supabase Studio locked down form state protection across replication and OAuth flows while the Realtime service adds group lookup to its admin dashboard.

javascript 18 shipped

@supabase Aug 2

SUPABASE POSTGRES HARDENS NIX BUILDS FOR ROLLING INSTANCE UPDATES

Supabase shipped a foundational infrastructure update that packages PostgreSQL environments for safer, zero-downtime deployments across its fleet.

javascript 2 shipped

Elsewhere on the wire

AI Agents Aug 6

LANGCHAIN HARDENS ANTHROPIC TOOL CALLING AND GIT CREDENTIALS AS OPENHANDS SHIPS 1.10.0

LangChain fixed a critical credential leak in evaluation runs while Anthropic tool schemas get proper fallback handling, as three major agent frameworks push releases across the ecosystem.

ai-agents 54 shipped

Local LLMs Aug 6

OLLAMA FIXES KV CACHE CORRUPTION, LLAMA.CPP HARDENS FILE SEARCH, VLLM KILLS MOE LEGACY CODE

Ollama patched a critical cache corruption bug that corrupts lazy snapshots during multi-request prefills, while llama.cpp hardened Windows junction traversal and vLLM removed 14 hardcoded MoE shards across quantization methods.