$ cat supabase/week/2026-10-26.log
the week in review · Oct 26 – Nov 1, 2026
AWS Marketplace becomes a purchase path for Supabase
By RepoJournal · composed from the cited sources · human-reviewed weekly · methodology
slim-services republishes postgres and realtime artifacts for arm64 and darwin, and supabase-js stops leaking undefined into Storage headers.
feat(studio): surface AWS Marketplace on billing and plan chooser supabase/supabase
Studio's plan chooser and billing now point eligible customers with an AWS spend commitment at Marketplace alongside the existing Stripe checkout, which stays unchanged. Teams buying against a PPA or EDP no longer have to reach Marketplace by memory at commitment time.
feat(www): add AWS Marketplace landing and pricing FAQ supabase/supabase
A canonical /aws-marketplace landing page splits self-serve (Pro and Team via Buy with AWS) from private offers. Both surfaces landed the same week, so the purchase path is now documented where customers decide rather than only in the product.
fix(storage): ignore undefined upload options supabase/supabase-js
Optional FileOptions passed as undefined used to overwrite the defaults, so raw uploads could send cache-control: max-age=undefined and content-type: undefined, and multipart uploads sent cacheControl as the string "undefined". If you construct options objects conditionally, upgrade rather than relying on the server to ignore the garbage.
chore: Bump nextjs to 16.4.3 (#52438) supabase/supabase
by supabase-vercel-tedd[bot]
next moves from 16.3.6 to 16.4.3 in pnpm-lock.yaml to clear a critical pnpm audit advisory, and rerunning pnpm audit confirmed it gone. The commit message notes no permanent changes beyond the lockfile.
fix(realtime): reconnect when a heartbeat goes unanswered supabase/supabase-csharp
The heartbeat timeout check in supabase-csharp never ran because hasPendingHeartbeat was never set, and had it been set, Stop would have closed the socket for good. Dead connections were still caught, but only by Websocket.Client's no-message timeout: 30 seconds, and up to 120 seconds after a few reconnects.
chore(master): release 8.5.1 supabase/supabase-csharp
8.5.1 ships the reconnect fix, plus caching of the X-Client-Info header per client assembly and Unity platform and runtime values reported correctly instead of as a Unix kernel string. Both matter if you filter server-side logs or analytics by client platform.
feat(studio): merge edge function Invocations into a scoped Logs tab supabase/supabase
With the unified logs preview on, an edge function's Logs tab renders the unified view scoped to that function, putting invocations and runtime output in one list. The separate Invocations and Logs tabs are gone.
mcp-server-supabase: v0.15.0 supabase/mcp
by supabase-releaser[bot]
mcp-server-supabase 0.15.0 adds submit_feedback and delete_feedback tools, and the same cycle made an expired confirmation surface a tool error instead of a generic JSON-RPC -32602, so clients can tell a timeout from a bad request.
$ ls supabase/week/ # the briefings behind this review
Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
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.