$ the-wire · showcase
Realtime rejoins the notebook: join limits, HTTP broadcast metrics, MCP write tools
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
11 people shipped this
Rodriguespn
@Rodriguespn
2 cited
pamelachia
@pamelachia
1 cited
jvoegele
@jvoegele
1 cited
edgurgel
@edgurgel
1 cited
supabase-evals-releaser
@supabase-evals-releaser
supabase-evals-releaser[bot]
@supabase-evals-releaser[bot]
Nik Richers
@nrichers
supabase-vercel-tedd[bot]
@supabase-vercel-tedd[bot]
Zammad Nasir
@ZammadNasir
claude
@claude
Sean Geoghegan
@seangeo
Realtime shipped per-socket join throttling and HTTP broadcast outcome recording, the MCP notebooks group exposed create, run and delete tools, and crawlers can finally see the /open-source page content.
feat: reject too many joins on a single socket supabase/realtime
A socket's join bucket now holds the tenant's max_channels_per_client and refills at CLIENT_JOINS_PER_SECOND (default 1), so a client can no longer occupy every channel slot in a single burst. The limit is gated per tenant behind the socket_join_limit feature flag.
feat: record broadcast request outcomes over HTTP supabase/realtime
The single and batch broadcast HTTP endpoints now record outcomes in realtime_client_requests_total, which previously only captured WebSocket sends, so the Broadcast error-rate SLO can include HTTP traffic. The PR's own summary calls the gap out directly: "Broadcasts sent over HTTP are not recorded, so the Broadcast error-rate SLO can't cover them."
fix: server-render /open-source repos and library docs code supabase/supabase
/open-source repo cards are now fetched via getStaticProps with hourly ISR instead of a GitHub call in useEffect, and the library docs install command and default code view dropped `dynamic(..., { ssr: false })`. Crawlers that do not execute JavaScript now see the content that two page templates used to withhold until hydration.
feat(notebooks): enable create_notebook and run_notebook tools supabase/mcp
The notebooks feature group registers create_notebook and run_notebook by default, and the internal unreleasedNotebookTools option and its plumbing are removed, so clients no longer need a server flag to write notebooks.
feat(notebooks): add delete_notebook tool with elicitation confirmation (#510) supabase/mcp
A new delete_notebook tool confirms through form elicitation like the other destructive tools and can be bypassed with skip_elicitations=delete_notebook; clients without form elicitation support are refused while confirmation is pending. Elsewhere: @hono/node-server moved from 1.19.17 to 2.1.5 as a lockfile-only fix for a moderate pnpm audit advisory patched in >=2.1.3, realtime added pubsub he...
Action items
- → Refresh the lockfile to @hono/node-server 2.1.5 to clear the moderate pnpm audit advisory patched in >=2.1.3 supabase/supabase [plan]
