RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

The Wire · Showcase

FLY.IO SUNSET HITS DASHBOARD, CLI DROPS TIMEOUT BOTTLENECK

By RepoJournal · Filed · About Supabase

Supabase is surfacing the Fly.io May 31 suspension directly in Studio with per-project impact breakdown, while the CLI finally kills the 10-second upload timeout that was choking storage streaming.

The Studio team shipped a self-correcting Fly.io deprecation banner [1] that shows affected projects and vanishes automatically once users migrate off the platform — no manual cleanup required. Meanwhile, the CLI fixed a critical bottleneck: storage uploads were timing out under load because the service gateway inherited a 10s timeout from legacy health-check code [2]. This wasn't a design choice; it was technical debt from code extraction years ago. On the frontend, Studio is hardening against React 19 regressions [3] by fixing four patterns that break under the new version today but pass on React 18 — landing the fixes now so the eventual upgrade is seamless instead of a separate cleanup pass. The CLI also shipped the TypeScript implementation of `supabase functions dev` [4], giving developers a managed local Supabase stack with Edge Runtime, file watching, and hot reload in a single command. Separately, domain hygiene: Supabase updated security documentation to use `supabase.com` instead of the legacy `supabase.io` address [5], ensuring researchers file disclosures to the right inbox.

Action items

References

  1. [1] feat(studio): Fly.io deprecation banner (#45778) supabase/supabase
  2. [2] fix(cli): drop full-request timeout from service gateway uploads (#5210) supabase/cli
  3. [3] fix(studio): pre-empt React 19 regressions in tests + Support form (#45784) supabase/supabase
  4. [4] feat: add `supabase functions dev` (#5186) supabase/cli
  5. [5] chore: updated the public facing docs to have the supabase.com instead of supabase.io (#45772) supabase/supabase

FAQ

What changed in Supabase on May 12, 2026?
Supabase is surfacing the Fly.io May 31 suspension directly in Studio with per-project impact breakdown, while the CLI finally kills the 10-second upload timeout that was choking storage streaming.
What should Supabase teams do about it?
Upgrade CLI to latest and test storage uploads — the timeout fix unblocks streaming • Check Studio for the Fly.io banner if you have projects on that platform — plan migrations before May 31 • Try `supabase functions dev` if you're running the TypeScript CLI — local development just got faster
Which Supabase repositories shipped on May 12, 2026?
supabase/supabase, supabase/cli

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • 14 famous open source orgs
  • One wire per day
  • Public, generic
  • Read on the web, when you remember

Your wire

  • Up to 1,500 of your repos - orgs, deps, vendors
  • Morning and evening briefs
  • Action items routed to your team
  • Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.