The latest major version of our .NET SDK, v8, is now available!
It brings every Supabase .NET package under a single repository with a unified version number, and provides a new extension for dependency injection.
This is the first release where all the packages ship together, so here is what to expect.
One version for every package#
Until now, the packages were scattered across multiple repositories, with their own version and lifecycle.
Gotrue was on v6.x.x, Realtime on v7.x.x, while the main package was on v1.x.x.
From v8.0.0, all packages share the same version number. Gotrue, PostgREST, Realtime, Storage, Functions, and the umbrella supabase package all release together.
When you see a version, you know exactly which packages and dependencies it pairs with.
On your side, it makes upgrades much easier.
Moving from v1.x.x to v8.0.0, in one go, is quite a bump and unusual.
It was our only option to guarantee lockstep-versioning: v8.0.0 was the first major bump available with Realtime already on v7.x.x.
It's a price we only have to pay once.
Everything in one repo#
All the packages now live in a single repository: supabase-community/supabase-csharp. It simplifies everything (especially cross-package work), whether it's contributions, maintenance or releases.
Previous repositories are still available but have been archived, and are now read-only. They also have been removed from our Community page.
New extension package#
A new package, Supabase.Extensions.DependencyInjection (available on NuGet), registers the Supabase client with the .NET service container and lets IHttpClientFactory manage its HttpClient.
If you run ASP.NET Core, this is the way to register Supabase into your app.
This package also follows lockstep-versioning, and therefore start at v8.0.0 as well.
Misc updates#
These did not deserve an entire section, but are worth mentioning:
- All serialization is handled with
System.Text.Jsoninstead ofNewtonsoft.Json. - Retry with backoff is built into every service package, and configurable.
- The client also accepts publishable and secret API keys.
- All packages target
netstandard2.1. If you use the umbrella package you were already on it, so nothing changes.
Upgrading from v7.x.x#
v8.0.0 being a major version, breaking changes are expected.
We wrote a migration guide to help you upgrade.
It covers all the breaking changes you might encounter, and how to address them.
Wrap up#
For the full list of changes, see the release notes.
Update your packages to v8.0.0, and let us know how it goes on GitHub. We're excited to hear your feedbacks.