Loading post…
Supabaseguillaume_faasAnnouncement
Introducing the unified Supabase .NET SDK
Summary
The Supabase .NET SDK v8 is now available, consolidating all packages under a single repository with a unified version number. Previously, packages like Gotrue, Realtime, and the main package were scattered across multiple repositories with separate versions and lifecycles, making upgrades complex. From v8.0.0, all packages—Gotrue, PostgREST, Realtime, Storage, Functions, and the umbrella package—share the same version, and previous repositories are archived as read-only. The jump from v1.x.x to v8.0.0 was necessary because Realtime was already on v7.x.x, and this ensures lockstep versioning going forward. A new dependency injection extension package registers the Supabase client with the .NET service container and lets IHttpClientFactory manage its HttpClient, starting at v8.0.0 as well. The update switches serialization from Newtonsoft.Json to System.Text.Json, adds configurable retry with backoff, accepts publishable and secret API keys, and targets netstandard2.1, with a migration guide available for breaking changes.
Context
Announcement of the unified Supabase .NET SDK v8, consolidating multiple packages into a single repository with a unified version number and adding a dependency injection extension.
Approach / What changed
Consolidating all Supabase .NET packages into a single repository with lockstep versioning, and providing a dependency injection extension for ASP.NET Core.
Takeaways
All Supabase .NET packages now share the same version number starting at v8.0.0, simplifying upgrades.
A new Supabase.Extensions.DependencyInjection package registers the client with the .NET service container and uses IHttpClientFactory.
The SDK switches from Newtonsoft.Json to System.Text.Json for serialization and adds configurable retry with backoff.
FAQ
What changed with the versioning of Supabase .NET packages?
All packages now share a unified version number starting at v8.0.0. Previously, packages like Gotrue and Realtime had separate versions. This lockstep versioning makes upgrades easier.
How do I register Supabase in an ASP.NET Core app?
Use the new Supabase.Extensions.DependencyInjection package. It registers the Supabase client with the .NET service container and lets IHttpClientFactory manage its HttpClient.
What breaking changes should I expect when upgrading?
The post mentions a migration guide covering all breaking changes. Key changes include switching to System.Text.Json and adding configurable retry with backoff.
Source and freshness
- Source
- supabase.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.