Supabase CLI v3 changes default behavior to local-first with hosted change confirmation
Users upgrading to CLI v3 will experience different default behavior requiring explicit confirmation for hosted database changes, potentially breaking existing automation and workflows that relied on direct hosted modifications
Evidence
+Breaking Change: Supabase CLI v3 is local by default and confirms hosted changes
ASP.NET Core dependency injection support added to Supabase .NET SDK
.NET developers using ASP.NET Core can now use dependency injection patterns with the Supabase .NET SDK, improving integration with modern .NET application architectures.
Evidence
+ASP.NET Core dependency injection for the Supabase .NET SDK
The .NET SDK now has official support status from Supabase, indicating maturity and reliability for .NET developers choosing to use it in production applications.
Evidence
+The Supabase .NET SDK is now officially supported
Framework adapters in @supabase/server package are deprecated
Developers using framework adapters in @supabase/server will need to migrate to alternative solutions. This affects any projects relying on these adapters for framework integration.
Evidence
+Framework adapters in @supabase/server are deprecated
OrioleDB moves to Public Beta with introduction of paid plans and paid features
Users can now access OrioleDB in Public Beta, but with paid subscription options available for the first time. This represents a shift from free/preview to commercial availability.
Evidence
+OrioleDB is now in Public Beta with paid plans and paid features
PostgreSQL 15.19 and 17.11 minor releases with potential breaking changes for ltree, pgcrypto, btree_gist, and custom operators
Supabase customers using PostgreSQL 15.x or 17.x may need to take action to ensure compatibility with ltree, pgcrypto, btree_gist extensions or custom operators after the upgrade
Evidence
+PostgreSQL 15.19 / 17.11 minor release — action may be required for ltree, pgcrypto, btree_gist, and custom operators
Users of Supabase's database replication feature will need to update their mental model and documentation references as the feature is now called Pipelines. This may affect product navigation, documentation, and user communication.
Extension version pinning deprecated: from 2026-08-05 explicit versions in create extension are ignored
Statements like create extension pgvector version '0.7.0' will install the project's default version and emit a warning starting 2026-08-05; a future release will reject them with an error. Migration scripts and IaC that pin Postgres extension versions on Supabase need updating.
Evidence
+Starting 2026-08-05, specifying an explicit version when creating or updating a Postgres extension on Supabase is deprecated. [...] the extension installs the default version on your project's Postgres instance, and the statement emits a warning. In a future release, announced separately in advance, these statements will be rejected with an error instead. [...] Pinning versions is now reserved for platform operations.
Realtime Broadcast now supports binary payloads over WebSockets, REST API, and database
Developers can now send and receive binary payloads (bytea) through Realtime Broadcast, reducing JSON overhead for sensor streams and image frames.
Evidence
+Supabase Realtime Broadcast now sends and receives binary payloads (bytea) over WebSockets, the REST API, and the database, cutting JSON overhead for sensor streams and image frames.
logs.all Management API endpoint being deprecated and replaced with new ClickHouse-backed logs endpoint
Users querying the logs.all endpoint must migrate to the new logs endpoint and convert queries to ClickHouse SQL dialect before September 23, 2026. This affects scripts, integrations, and tooling calling this endpoint directly.
Evidence
+The logs.all Management API endpoint is being removed on 23rd September 2026 (Wednesday), two months from this announcement. Log querying moves to a new ClickHouse-backed logs endpoint. The new endpoint accepts ClickHouse SQL only.