Who contributed to Supabase on October 28, 2026?

9 developers shipped this update, including Kody Jackson, SaxonF, lukas-bernert, alaister, github-actions[bot], nyannyacha, barryroodt, and supabase-releaser, and 1 more.

What were the notable Supabase updates?

feat(studio): merge edge function Invocations into a scoped Logs tab, fix(studio): reload once on chunk load failures, and fix(base/worker): hand a booted worker to requests queued behind it.

Oct 28, 2026

$ the-wire · showcase

Edge functions get unified Logs, Studio reloads once on chunk failures

By RepoJournal · Filed 06:56 UTC on October 28, 2026 · About Supabase · Composed from the cited sources · methodology

9 people shipped this

SaxonF @SaxonF 2 cited

alaister @alaister 1 cited

nyannyacha @nyannyacha 1 cited

barryroodt @barryroodt 1 cited

Kody Jackson @kodster28

lukas-bernert @lukas-bernert

github-actions[bot] @github-actions[bot]

supabase-releaser @supabase-releaser

Pranshul Soni @PranshulSoni

Supabase's Studio and edge-runtime both shipped recovery and consolidation work today: log views merged into one scoped surface, failed chunk loads self-healing, and queued requests no longer stalling behind a booting worker.

feat(studio): merge edge function Invocations into a scoped Logs tab supabase/supabase

by SaxonF

With the unified logs preview enabled, an edge function's Logs tab now renders the unified logs view scoped to that function, putting invocations and runtime output in one list and retiring the separate Invocations and Logs tabs. `UnifiedLogs` gains `scope`, `hasFilterSideBar`, `offeredFilters` and `columnPreferencesKey`, and the function tab keeps its column and panel layout separate from the ...

fix(studio): reload once on chunk load failures supabase/supabase

by alaister

When a lazy-loaded JS or CSS chunk fails, Studio now reloads the page once instead of stranding users on the global error screen until a manual refresh, in both runtimes. The PR notes a reload is the only reliable recovery because WebKit caches a failed module fetch in the document's module map, so every later `import()` of that URL fails instantly until the page is replaced.

fix(base/worker): hand a booted worker to requests queued behind it supabase/edge-runtime

by nyannyacha

Under the per-worker policy, requests arriving while a function's only worker was still booting waited until a request on that worker finished, then failed with "worker did not respond in time" once the wait timeout expired; a failed boot also left them waiting out the full timeout. Waiters are now woken when a per-worker worker is registered, so queued requests get handed the booted worker ins...

feat(studio): slim edge function detail layout and move header to Overview supabase/supabase

by SaxonF

The edge function detail page drops its page header for breadcrumbs plus `PageNav` tabs, giving Logs and Code the full height below the tabs, with the function name, invoke URL and last deploy moving into an Overview header that also holds the chart period selector. Both the new and legacy Overview default to a 1 hour period instead of 15 minutes.

fix(mcp-server-supabase): return a tool error when a confirmation expires supabase/mcp

by barryroodt

An expired confirmation form previously surfaced as a generic JSON-RPC `-32602` "Invalid or expired requestState", which clients could not distinguish from a broken server and the model got no signal to retry; it now returns a tool error. The reporter traced this to a support ticket where Codex answered a `create_branch` cost confirmation late.