Supabase Changelog

The .NET SDK now emits traces and metrics for Auth, Postgrest, Storage, and Functions, collectable with OpenTelemetry and exportable to any observability backend.

Supabase will disable a subset of TLS 1.2 ciphers on project HTTP APIs on November 10, 2026. Clients that don't support modern standards, under 0.0001% of traffic, will fail to connect.

The .NET SDK now ships an ASP.NET Core dependency injection package, where a single method registers the main client and all sub-clients.

The .NET SDK for Supabase is now officially supported and is the recommended way to build on Supabase from any .NET platform, including ASP.NET, Blazor, MAUI, Unity, and Azure.

status.supabase.com now runs on incident.io, and email subscribers carry over. SMS, Slack, and webhook subscribers must resubscribe, though the new page supports only email, RSS, and Slack.

Personal access tokens can now be scoped to specific projects or organizations, granting only the permissions needed on the Management API, MCP server, and CLI.

The Hono, H3, Elysia, and NestJS adapters in @supabase/server are deprecated and will be removed on December 1, 2026. Move to the framework bridges described in the frameworks guide.

Organization invites on Team and Enterprise plans now support the No access role, so admins can default new members to zero project access.

The official Supabase Go SDK is in public alpha with an initial feature set for verifying end-user access tokens and querying the database as that user under Row Level Security.

Multigres runs Supabase with multi-AZ high availability, automatic failover, and scalable connection pooling. It is available in Private Alpha to selected Pro, Team, and Enterprise organizations.

OrioleDB projects can now be created on Free, Pro, Team, and Enterprise plans with paid features and standard Postgres pricing. Existing alpha projects are unchanged.

@supabase/middleware 1.0.0 is stable, offering typed, composable middleware for fetch handlers that runs wherever fetch runs, standalone or inside a framework through a short bridge.

Supabase Logs is moving to usage-based pricing, with more than 90% of projects within the included limits and a grace period running through early 2027.

The Postgres minor upgrade to 15.19 and 17.11 fixes 44 CVEs, but ltree and btree_gist indexes may need reindexing and pgcrypto data encrypted with legacy ciphers needs re-encryption.

Database Replication is now Database Pipelines in the dashboard, with existing Replication URLs redirecting to the new location. No API or pipeline behavior has changed.

Supabase Advisors now include service health checks for error rates across Auth, Storage, Edge Functions, and Data APIs, each with a severity level and a direct link to investigate.

Supabase published prepared prompts for four monitoring roles, ready to run in Claude Routines, Codex, Cursor Automations, or any environment you choose, so an agent can watch your project.

Read replicas have moved under Project Settings → Infrastructure. Database → Replication now only covers Pipelines destinations, with no API changes.

Daily backups were occasionally skipped silently when a scheduling window timed out; backup scheduling now retries and recovers automatically.

A physical restore could leave a project with stale database credentials, causing authentication failures. Restores now reapply current credentials afterward.