Supabase Announces Unified .NET SDK Version 8

AIDeveloper44 Team

Consolidating the .NET Ecosystem

Supabase recently announced the release of version 8.0.0 of its .NET SDK, representing a significant shift in how the organization manages its C# libraries. By moving every package into a single unified repository, the development team aims to simplify the contribution, maintenance, and release lifecycles for .NET developers interacting with the Supabase platform.

Previously, individual packages like Gotrue, Realtime, and Postgrest were managed in separate repositories, each following independent versioning schemes. This fragmented approach often led to complexity for developers trying to track compatibility between dependencies. With the v8.0.0 release, all core components—including Gotrue, Postgrest, Realtime, Storage, Functions, and the primary umbrella package—now share the same version number, ensuring they ship in lockstep.

New Dependency Injection Support

A notable addition in the version 8 update is the introduction of Supabase.Extensions.DependencyInjection. This new package facilitates the registration of the Supabase client within the standard .NET service container. For developers building applications with ASP.NET Core, this allows for seamless integration, enabling IHttpClientFactory to manage the underlying HttpClient instances efficiently. The new extension package also adheres to the unified versioning model, beginning at v8.0.0.

Key Technical Migrations and Breaking Changes

The transition to version 8 introduces several breaking changes that necessitate updates to existing codebases. Most notably, the SDK has transitioned its primary serialization engine from Newtonsoft.Json to System.Text.Json across all packages. This alignment with modern .NET defaults offers improved performance and consistency throughout the library.

Furthermore, the target framework for all packages has been updated to netstandard2.1. This change means that the SDK no longer supports netstandard2.0, which was previously the ceiling for older .NET Framework projects and specific older runtimes such as older versions of Mono, Xamarin, or Unity. Developers relying on these older environments will need to migrate to a netstandard2.1-capable target, such as .NET Core 3.0 or .NET 5 and above.

Additional architectural improvements include standardized retry and backoff logic, which is now built into every service package. This feature is configurable, allowing developers to fine-tune how the SDK handles network failures and transient errors without implementing custom logic in their application layer.

Enhanced Functionality and Cleanup

The cleanup of the repository structure has resulted in the archiving of several older, individual repositories, which are now designated as read-only. This centralization is designed to foster a more predictable development experience. Developers interested in the complete list of changes, including specific bug fixes and performance enhancements, can refer to the detailed release notes provided on the official GitHub repository.

Supabase has also published a migration guide to assist users in upgrading from v7.x.x to v8.0.0. Given the scale of these changes, the organization recommends reviewing the documentation thoroughly to address potential breaking changes in API surface areas, such as the modified return types in IPostgrestTable.Delete and adjustments to how OAuth state is handled in Gotrue. By standardizing the ecosystem, Supabase intends to provide a more reliable and maintainable toolset for .NET developers building modern, high-concurrency services.

Enjoyed this?

Get more posts like this delivered to your inbox.

Subscribe