124 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-06-16
stories 64

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

GRPC PATCHES AUTHORIZATION BYPASS AS SUPABASE MODERNIZES REALTIME STACK

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

A critical authorization bypass in gRPC 1.56 to 1.79.2 could let attackers bypass request validation, and Supabase is patching across benchmarks while shipping realtime improvements.

The grpc-go team fixed a server-side authorization bypass where malformed :path headers missing the leading slash could bypass authorization checks [1]. Supabase's benchmarks repo jumped from gRPC 1.56.3 to 1.79.3 to close this gap [1]. On the realtime front, the team is dropping its fork of gen_rpc now that all upstream PRs hit the original EMQX repository [2], reducing maintenance burden. Svelte got two separate bumps in benchmarks: a major jump from 4.2.19 to 5.51.5 [3] followed by patch updates to 5.55.7 addressing XSS on hydration [4]. The supabase-js client in realtime bumped to v2.108.2, fixing auth session refresh failures and clarifying httpSend() errors [5]. On the docs side, external replication (ETL) terminology is now standardized across the platform [6], Edge Functions got a new error codes reference guide [7], and High Availability projects on Multigres now show which features (Realtime, Replication, PITR) are unavailable [8].

Action items

References

  1. [1] build(deps): bump google.golang.org/grpc from 1.56.3 to 1.79.3 in the go_modules group across 1 directory ↗ supabase/benchmarks
  2. [2] fix: update gen_rpc to original fork ↗ supabase/realtime
  3. [3] build(deps-dev): bump svelte from 4.2.19 to 5.51.5 in /web in the npm_and_yarn group across 1 directory ↗ supabase/benchmarks
  4. [4] build(deps): bump the npm_and_yarn group across 1 directory with 6 updates ↗ supabase/benchmarks
  5. [5] chore: update @supabase/supabase-js to v2.108.2 ↗ supabase/realtime
  6. [6] Standardize external replication (ETL) docs ↗ supabase/supabase
  7. [7] docs(functions): add error codes page ↗ supabase/supabase
  8. [8] chore: Disable some of the Studio features on Multigres projects ↗ supabase/supabase

Quick answers

What shipped in Supabase on June 16, 2026?
A critical authorization bypass in gRPC 1.56 to 1.79.2 could let attackers bypass request validation, and Supabase is patching across benchmarks while shipping realtime improvements. In total, 30 commits, 33 pull requests, and 1 releases landed.
Who contributed to Supabase on June 16, 2026?
6 developers shipped this update, including dependabot[bot], edgurgel, supabase-libs-pr-manager[bot], iambriccardo, kallebysantos, and ivasilov.
What were the notable Supabase updates?
build(deps): bump google.golang.org/grpc from 1.56.3 to 1.79.3 in the go_modules group across 1 directory, fix: update gen_rpc to original fork, and build(deps-dev): bump svelte from 4.2.19 to 5.51.5 in /web in the npm_and_yarn group across 1 directory.