$ the-wire · showcase
Edge function paths stop breaking MCP listing, evals move off Git
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
12 people shipped this
mattrossman
@mattrossman
1 cited
claude
@claude
1 cited
claude[bot]
@claude[bot]
1 cited
Colum Ferry
@Coly010
1 cited
AndrewJackson2020
@AndrewJackson2020
1 cited
supabase-evals-releaser
@supabase-evals-releaser
dependabot
@dependabot
Pedro Rodrigues
@Rodriguespn
supabase-releaser
@supabase-releaser
Barry Roodt
@barryroodt
Vaibhav
@7ttp
github-actions[bot]
@github-actions[bot]
The day's load-bearing fixes are unglamorous ones: MCP's edge function tools stop crashing on Deno 2 deploys, and the evals site reads its numbers from Braintrust instead of a committed snapshot.
fix: tolerate non-URL edge function paths in api platform supabase/mcp
list_edge_functions and get_edge_function threw TypeError: Invalid URL whenever the Management API returned an entrypoint_path or import_map_path that was not a file:// URL, which Deno 2 deploys do, so a single such function broke listing for the whole project. The fix falls back to the raw path, matching what the hosted tooling already does.
feat: serve benchmark results from Braintrust supabase/evals
The evals site used to read pinned experiment IDs from a separate committed JSON snapshot even though results were already being uploaded to Braintrust. It now fetches from pinned Braintrust experiment IDs at build time, so one model's results can be refreshed by updating its experiment ID without rerunning the others.
chore(repo): fix the API package sync and a CodeQL alert (#7416) supabase/cli
The hourly API Package Sync had failed every run since 20 Oct because the Management API spec now sets contentEncoding: "binary" on the ESZIP upload body, which Effect's OpenAPI 3.0 converter rejects. Both contentEncoding and contentMediaType are annotations and format: binary already says the same thing, so the sync sanitizes them out.
fix(ci): pin Node 24 in mise.toml (#504) supabase/mcp
Node 26 becoming LTS made node = "lts" in mise.toml resolve outside mise.lock, so the locked install at the mise setup step failed on every PR. mise.toml now pins Node 24, matching the locked 24.15.0.
refactor: add schema snapshot supabase/vault
With SQL install and migration paths merged, the extension lost the ability to diff its own state over time. This adds a script and CI job that snapshots the extension schema to text, which is how the pg_net migration drift was caught. Also landed: seven more CLI test files brought under effect lint, and portable analytics v1.54.3-r0 and postgres 17.11.0.016 artifacts for linux/amd64, linux/arm...
