151 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-10-01
stories 84

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Self-hosted function errors get structured, gateways get key handling

By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology

Self-hosted Edge Functions pick up structured 5xx errors and API key handling on both gateways, while supabase-csharp closes a Windows file-lock bug and the eval suite gains its first CLI arm.

feat(self-hosted): add function runtime errors supabase/supabase

by luizfelmach

The self-hosted main worker used to return runtime exceptions as generic 500 responses; it now returns structured errors for routing and runtime failures, adds error headers to function 5xx responses, and aligns runtime and gateway timeouts for long-running and streaming requests.

feat(self-hosted): add api gateway logic for functions supabase/supabase

by aantti

The /functions/v1/ route in both self-hosted gateways, Kong and Envoy, previously passed requests through with no key handling; it now handles API keys, and the Edge Functions main worker has been updated to use it. Expect different behavior for requests that arrive without an apikey or Authorization header.

fix(storage): close the local file after a resumable upload supabase/supabase-csharp

by fresh55

UploadOrResume(localPath) never closed the file handle it opened, so the file stayed locked until the GC ran. On Windows that meant deleting or moving a file right after upload threw an IOException, which is why the UploadOrResume E2E test failed there; the handle is now closed after the upload completes.

fix(functions): return null from `Invoke<T>` for an empty body supabase/supabase-csharp

by fresh55

Invoke<T> returns null for an empty response body again instead of throwing, restoring the prior behavior for callers that treat an empty body as a normal result.

chore: Bump vulnerable deps supabase/supabase

by ivasilov

A broad dependency pass bumps devalue, mermaid, @faker-js/faker, brace-expansion, undici, fast-uri and markdown-it, and dedupes rolldown, vite and react-router across Lite Studio, Studio and the Vue block. Per the PR summary, the changes touch development and build tooling and do not alter behavior.

chore: refresh eval results supabase/evals

by supabase-evals-releaser

The long tail stayed routine: apps/web/src/data/eval-results.json refreshed from the latest automated eval run, the new build-database-002-stack-lifecycle CLI eval landed to measure whether agents in Docker-less sandboxes report the real blocker or reach for install workarounds, and slim-services cut realtime v2.140.5-r0 and storage v1.79.28-r0/r1 artifacts for linux/amd64, linux/arm64 and darw...

Quick answers

What shipped in Supabase on October 1, 2026?
Self-hosted Edge Functions pick up structured 5xx errors and API key handling on both gateways, while supabase-csharp closes a Windows file-lock bug and the eval suite gains its first CLI arm. In total, 37 commits, 37 pull requests, and 10 releases landed.
Who contributed to Supabase on October 1, 2026?
10 developers shipped this update, including supabase-evals-releaser, Coly010, supabase-evals-releaser[bot], github-actions[bot], Miranda Limonczenko, Pamela Chia, luizfelmach, and ivasilov, and 2 more.
What were the notable Supabase updates?
feat(self-hosted): add function runtime errors, feat(self-hosted): add api gateway logic for functions, and fix(storage): close the local file after a resumable upload.