$ the-wire · showcase
Next 16.4.3 clears a critical advisory, and list_tables stops reordering columns
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
Supabase's main repo bumped next to 16.4.3 to clear a critical pnpm audit advisory, the MCP server fixed a real correctness bug in list_tables, and slim-services republished the postgres, realtime, storage and analytics runtime images.
chore: Bump nextjs to 16.4.3 (#52438) supabase/supabase
by supabase-vercel-tedd[bot]
The lockfile bump from next 16.3.6 to 16.4.3 was applied with pnpm tsx scripts/fix-audit-vulnerability.ts next and re-audited to confirm the critical advisory is gone, with no permanent override left behind. Package manifests are unchanged; the other lockfile deltas are transitive @next/* and sharp 0.35.5.
fix(pg-meta): order list_tables columns by ordinal position supabase/mcp
array_agg in coalesceRowsToArray followed heap scan order, so an ALTER COLUMN, which moves a column's pg_attribute row to the end of the heap, could make list_tables return columns out of order. The fix adds an optional orderBy argument and sorts by columns.ordinal_position, with a test that alters columns and checks the order holds.
postgres 17.11.0.008-orioledb-r0 supabase/slim-services
by github-actions[bot]
slim-services published portable, smoke-tested runtime artifacts for postgres 17.11.0.008-orioledb-r0 across linux/amd64, linux/arm64 and darwin/arm64, available as an immutable image reference under ghcr.io/supabase/cli/postgres for reproducible pulls.
fix(core): report Unity version, platform and runtime in X-Client-Info supabase/supabase-csharp
The X-Client-Info header used to report platform as Unix 5.15.189.13 and runtime as dotnet on Unity Android IL2CPP builds; it now reports Android, il2cpp or mono, and a framework-version read from UnityEngine.Application, e.g. 6000.3.21f1. Anyone segmenting analytics or support triage by client platform should expect the new values.
chore: Bump `launch-editor` to fix a vulnerability (#52442) supabase/supabase
by supabase-vercel-tedd[bot]
Also in the same audit sweep: launch-editor went from 2.14.1 to 2.14.2 in pnpm-lock.yaml to pick up the patch for a high-severity advisory, applied via the same fix-audit-vulnerability.ts script with no package.json edits.
fix: keep experiment names separate from suites supabase/evals
Quieter elsewhere: the evals hotfix restores bare experiment names while leaving result paths suite-qualified, correction the metadata regression from the earlier suite-prefixed naming, and mcp, evals, and the docs navigation work (a new nav-check test, Option 1 IA behind the docs-ia-mvp-v1 flag) rounded out the day.
Action items
- → Upgrade next to 16.4.3 and re-run pnpm audit to confirm the critical advisory is cleared supabase/supabase [plan]
- → Upgrade launch-editor to 2.14.2 or later wherever it resolves transitively supabase/supabase [plan]