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-10-25
stories 4
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Eval results refreshed, Management API types regenerated

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

supabase-evals-releaser supabase-evals-releaser[bot] supabase-releaser[bot]
3 people shipped this
supabase-evals-releaser @supabase-evals-releaser 1 cited supabase-evals-releaser[bot] @supabase-evals-releaser[bot] 1 cited supabase-releaser[bot] @supabase-releaser[bot] 1 cited

Both repos saw automated pipeline output land rather than hand-written changes: supabase/evals republished its results file from the latest automated run, and supabase/mcp resynced its Management API types against the current OpenAPI specs.

chore: refresh eval results supabase/evals

by supabase-evals-releaser

The releaser bot rewrote apps/web/src/data/eval-results.json from the latest automated eval run, so the published scores on the evals site now reflect that run rather than the previous one. Anyone reading the dashboard should treat numbers from before this refresh as stale.

chore: regenerate management API types (#484) supabase/mcp

by supabase-releaser[bot]

The Sync Management API Types workflow regenerated the client types in supabase/mcp from the current v1 and v2 OpenAPI specs at api.supabase.com. If the Management API schema shifted under you, the MCP server's types now track it; a local build against the older types may need a reinstall.

chore: refresh eval results (#433) supabase/evals

by supabase-evals-releaser[bot]

The commit record for the evals refresh, co-authored by mattrossman, carries no additional changes beyond the JSON update already described.

$ 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 October 25, 2026?
Both repos saw automated pipeline output land rather than hand-written changes: supabase/evals republished its results file from the latest automated run, and supabase/mcp resynced its Management API types against the current OpenAPI specs. In total, 2 commits and 2 pull requests landed.
Who contributed to Supabase on October 25, 2026?
3 developers shipped this update, including supabase-evals-releaser, supabase-evals-releaser[bot], and supabase-releaser[bot].
What were the notable Supabase updates?
chore: refresh eval results, chore: regenerate management API types (#484), and chore: refresh eval results (#433).
♥

$ 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.