RepoJournal
Supabase @supabase
174 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-11-02
stories 28
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Realtime 2.151.0 measures join budgets, dbdev pulls a critical Next.js patch

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

dependabot realtime-release-bot[bot] seangeo Prashansa-K supabase-cli-releaser supabase-evals-releaser supabase-evals-releaser[bot]
11 people shipped this
dependabot @dependabot 1 cited realtime-release-bot[bot] @realtime-release-bot[bot] 1 cited seangeo @seangeo 1 cited Prashansa-K @Prashansa-K 1 cited supabase-cli-releaser @supabase-cli-releaser 1 cited supabase-evals-releaser @supabase-evals-releaser supabase-evals-releaser[bot] @supabase-evals-releaser[bot] Raminder Singh @imor edgurgel @edgurgel Henry Su @hsusul supabase-cli-releaser[bot] @supabase-cli-releaser[bot]

Realtime shipped per-client join accounting gated behind a feature flag, the CLI's local stack moved to realtime v2.151.3-r0 and a newer studio build, and dbdev took a Next.js 16.4.1 bump that carries critical security fixes.

v2.151.0 supabase/realtime

by realtime-release-bot[bot]

v2.151.0 lands the per-client join measurement that edgurgel's change describes as a join budget of max(10, 1 x the tenant's connected clients on this node) joins per second; the budget currently only records joins that exceed it, and joins still succeed. It runs only for tenants with the node_join_budget feature flag on, and exists to surface tenants whose clients reconnect or rejoin channels ...

chore(rollcall): set up transport behaviour and use it to handle messages supabase/realtime

by seangeo

The first part of the Rollcall transport adapter: a behaviour plus null and test implementations, passed into a tracker via init parameters. On init the tracker joins the transport and unwraps incoming messages through it.

ci(cli): add a full benchmark for integration-heavy commands supabase/cli

by Prashansa-K

/bench full dispatches the integration-heavy tier, the commands that need a running local stack or database, on the pull request's branch; it stays report only and is not a required check. It re-measures that benchmark and refreshes the lightweight benchmark comment only when that comment is behind the head commit.

chore(deps): bump next from 16.3.8 to 16.4.1 in /website in the npm_and_yarn group across 1 directory supabase/dbdev

by dependabot

next moves from 16.3.8 to 16.4.1 in /website, a release the upstream notes describe as containing security fixes, including a critical advisory. The maintainers merged it, and the change is scoped to dbdev's website directory.

chore(stack): bump realtime to v2.151.3-r0 supabase/cli

by supabase-cli-releaser

The remaining work is maintenance: cli's stack bumps realtime from v2.150.2-r0 to v2.151.3-r0 and studio to 2026.11.02-sha-a05e7ec-r0, a realtime fix allows the documented maximum of 500 refs in bulk tenant health, and the evals results JSON was refreshed from the latest automated run.

$ ls supabase/reviews/ # the step-back reads

the week in review Realtime 2.151 begins capping joins per socket the month in review Realtime patches cross-tenant private channel leak
Full archive → Weekly reviews →

Quick answers

What shipped in Supabase on November 2, 2026?
Realtime shipped per-client join accounting gated behind a feature flag, the CLI's local stack moved to realtime v2.151.3-r0 and a newer studio build, and dbdev took a Next.js 16.4.1 bump that carries critical security fixes. In total, 14 commits, 10 pull requests, and 4 releases landed.
Who contributed to Supabase on November 2, 2026?
11 developers shipped this update, including supabase-evals-releaser, supabase-evals-releaser[bot], dependabot, Raminder Singh, realtime-release-bot[bot], seangeo, edgurgel, and Henry Su, and 3 more.
What were the notable Supabase updates?
v2.151.0, chore(rollcall): set up transport behaviour and use it to handle messages, and ci(cli): add a full benchmark for integration-heavy commands.
♥

$ log @supabase --recent

Studio tightens the MFA removal path; realtime preps a presence swap 34 shipped Eval results refreshed from the latest automated run 2 shipped Studio stops mangling column comments, eval version encoding fixed 76 shipped MCP stops prompting on read-only EXPLAIN, bounds notebook cost 157 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.