Supabase Release Notes
144 release notes curated from 45 sources by the Releasebot Team. Last updated: Nov 13, 2026
- Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 13, 2026
Backup sign-in options for Supabase accounts
Supabase adds backup password sign-in and MFA recovery codes, helping users regain account access if they lose an OAuth provider or authenticator.
Account Security
Account Security in the dashboard has two backup sign-in options for your Supabase account.
If you only sign in with an OAuth provider, such as GitHub or ChatGPT, you can add a password for your account email. If you lose access to that provider, sign in with your email and password instead.
When you set up MFA, you get 10 single-use recovery codes. If you lose your authenticator app, use a code to complete the MFA step. Account Security shows how many codes are left and lets you regenerate them.
No action required, but we recommend setting up both. See the MFA guide for details.
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Correlated Logs
Supabase releases correlated logs in Beta, linking events by request, trace, and user so teams can trace activity across Studio and Auth. CLI v3 also brings interactive hosted log inspection, filtering, and JSON output to the terminal.
What's new
Correlated Logs is now available in Beta. The Studio Logs tab now lets you connect log events using three meaningful identifiers: requestId, traceId, and userId.
Every log item now has four tabs: a structured Overview, Raw JSON, and two contextual tabs that appear when relevant:
- Timeline — where a requestId is present, fetches all log items for that request and shows them as a timeline. You can select any item in the chain to see its details and navigate back to the full list.
- User — where a log item is associated with an authenticated user, shows their details and links directly to that user in Auth. From the Auth user page, you can view all their logs in the same unified view.
You can also filter the logs list by user attributes to see all log items for a specific user, in the same way you filter by requestId or traceId.
For AI agents using the Supabase MCP server, the query_logs tool supports the same identifiers. See MCP debugging.
How to use it
Open the Logs tab in your project dashboard and filter by requestId, traceId, or user attributes. Click into any log item to see the Timeline or User tab where available.
To send a traceId from your application, see client-side tracing.
Logs in CLI v3
Inspect hosted logs in your terminal:
supabase logs --remote --service postgres --level error --since 30mFilter by service, severity, or time range. Use --from and --to for fixed UTC bounds.
In an interactive terminal, use the up and down arrows to select a row, Enter to inspect it, C to copy the full record as JSON, and L to load newer logs on demand.
For scripts and agents, --output-format json and --output-format stream-json read once and exit. Query hosted logs with --sql or load SQL with --file.
The command defaults to local logs, which require the experimental stack runtime.
Read the CLI logs guide for setup and examples.
Why we built this
When something goes wrong, the signal is spread across log items from different services, and tracking it back to a specific request or user means cross-referencing timestamps by hand. These connections should be a click away.
This is a Beta release. Try it and share feedback in the GitHub Discussion below.
Original source All of your release notes in one feed
Join Releasebot and get updates from Supabase and hundreds of other software products.
- Nov 6, 2026
- Date parsed from source:Nov 6, 2026
- First seen by Releasebot:Nov 7, 2026
Breaking Change: supabase-flutter v3 brings type safety to the whole API surface
Supabase releases supabase-flutter v3 as a major update, now available in dev prereleases, with end-to-end typed database APIs, Dart-native data types, and coding-agent migration skills. The additive typed API supports gradual adoption, while v2 receives critical fixes for six months after stable launch.
supabase-flutter v3 is the next major version of the Supabase client libraries for Flutter and Dart. You can try it today through the 3.0.0-dev prereleases on pub.dev. The stable 3.0.0 release is planned for November 11, 2026.
What you get
Types across the whole client.
supabase gen types --lang dartturns your database schema into a Dart file with a row, insert, and update type for every table. The newsupabase.table(Books.table)API uses them end to end: selects returnList<BooksRow>instead ofList<Map<String, dynamic>>, a filter such asBooks.price.lt(20)only accepts a value of the column's type, writes take generated insert and update types, embedded selects follow foreign keys, andstream()emits typed rows. Postgres functions get typed methods onsupabase.rpc. Beyond the database, the connection state of the realtime client, channel results, AuthState, and every service exception are typed too. A renamed column breaks your build, not your users' sessions.An API that reads like Dart. Timestamps are
DateTime, URLs areUri, durations areDuration, realtime listeners are Streams, AuthState is a sealed class you can switch over exhaustively, and every service exception extends one SupabaseException base.Skills for coding agents. The supabase, supabase_flutter, supabase_typegen, and supabase_test packages ship package skills for Claude Code, Cursor, Gemini, and Copilot. They teach your agent the v3 API instead of the v2 code it was trained on, and include a skill that carries a v2 project through the upgrade.
The typed API is additive. from() keeps working on the same client, so you can move one table at a time. It is marked @experimental while its shape settles.
Why v3 breaks v2 code
Large parts of v2 were ported directly from supabase-js. Timestamps and URLs were strings, realtime used callbacks, and order() sorted descending by default, the opposite of SQL, with nothing in the analyzer or the results to reveal it. A major version is the only moment these shapes and defaults can change, so v3 changes all of them at once. You upgrade once instead of absorbing a series of smaller breaks.
Who is affected
Every Dart and Flutter project on supabase_flutter or supabase v2 that upgrades to v3.
Projects that depend directly on gotrue, realtime_client, storage_client, or functions_client. These are renamed to supabase_auth, supabase_realtime, supabase_storage, and supabase_functions, and the old packages are marked discontinued on pub.dev when v3 ships. If you only depend on supabase_flutter or supabase, your dependencies and imports stay the same.
Projects that use a third-party package built on supabase_flutter v2. You can upgrade once that package releases a v3-compatible version.
Self-hosted projects running a GoTrue older than API version 2024-01-01. v3 only reads the newer error codes.
What happens if you take no action
Nothing changes. A ^2.x version constraint never resolves 3.0.0, and pub never picks a prerelease unless you ask for one. v2 keeps receiving security and critical fixes for 6 months after the stable 3.0.0 release. New features only land in v3.
Changes the compiler will not catch
Most of the upgrade shows up as compile errors. Some changes do not, such as the default sort direction of order() and how apps on v2 and v3 exchange realtime broadcasts, so check the full list of changes the compiler will not catch in the migration guide before you ship.
Migration steps
Read the changes the compiler will not catch. Add ascending: false to every order() call that relies on descending order, while you are still on v2.
Bump supabase_flutter or supabase to ^3.0.0 in pubspec.yaml. Replace direct dependencies on gotrue, realtime_client, storage_client, and functions_client with their renamed packages.
Install the package skills, for example with
dart run skills@ get -p supabase_flutter, then ask your coding agent to run the migration skill if you work with one.Fix the compile errors with the migration guide. For example, anonKey on Supabase.initialize becomes publishableKey. Your existing anon key is still a valid value.
Go through the changes the compiler will not catch one by one, and release every app that shares a realtime broadcast channel at the same time.
Optionally, add supabase_typegen as a dev dependency, generate your types with Supabase CLI 2.122.0 or newer, and move your queries from from() to table().
Rollout timeline
Date Milestone User action Now v3 available as 3.0.0-dev prereleases on pub.dev Optional: try v3 and report issues on GitHub 2026-11-11 3.0.0 stable. gotrue, realtime_client, storage_client, and functions_client are marked discontinued on pub.dev Upgrade by following the migration steps 6 months after the stable release v2 stops receiving security and critical fixes Finish the upgrade to v3Questions or problems with the upgrade? Open an issue on supabase-flutter or contact Supabase support.
Original source - Nov 4, 2026
- Date parsed from source:Nov 4, 2026
- First seen by Releasebot:Nov 13, 2026
Breaking Change: Supabase CLI v3 is local by default and confirms hosted changes
Supabase releases CLI v3 with local-stack defaults, confirmation before hosted changes, and removed deprecated commands; CI may need updates.
Supabase CLI v3 targets your local stack by default, asks before it changes a hosted project, and removes deprecated commands. Update your CI before you upgrade, or pin v2.
Original source - Nov 4, 2026
- Date parsed from source:Nov 4, 2026
- First seen by Releasebot:Nov 5, 2026
Breaking Change: Supabase CLI v3 is local by default and confirms hosted changes
Supabase releases CLI v3 with safer, consistent defaults: commands target the local stack unless directed to a hosted project, hosted changes require confirmation, and configuration follows a unified precedence. The major upgrade also changes schema diff behavior and removes deprecated commands, requiring CI and deployment updates.
Supabase CLI v3.0.0 is the next major version of the Supabase CLI. npm, Homebrew, Scoop, the Linux packages, and supabase/setup-cli now install it by default. It changes which project a command runs against, when a command asks for confirmation, and where configuration values come from. Most pipelines that deploy with the CLI need a small change before they upgrade.
What changed
Database commands target your local stack by default. db push, db pull, db dump, migration list, gen types, and the storage commands run against the local stack unless you pass --remote. One --remote flag replaces --linked, --project-ref, and --db-url, which still work but are deprecated.
Every command that changes a hosted project asks for confirmation first, and the default answer is No. When the CLI can't ask, as in CI, the command fails unless you pass --yes. Piping y into a command no longer confirms it.
Flags and environment variables override config.toml, including [remotes.] blocks. Every value resolves in the same order: flag, shell environment, project env files, config file, then default.
pg-delta is the default schema diff engine, so the SQL that db diff and db pull generate can change.
Deprecated commands, flags, config keys, and environment variables are removed. A removed command or flag exits with code 1 and prints its replacement. This includes the [inbucket] config section, which is now [local_smtp].
The CLI ships as a single supabase executable. The separate supabase-go executable is no longer installed.
Two smaller changes can affect a production project. config push now applies [auth.sms] enable_confirmations as written. secrets unset defaults to No and needs --all to remove every secret.
Why we made this change
In v2, some database commands defaulted to the linked project and others to the local stack, and four different flags chose a target. A command run without a flag could reach a production database. Many hosted changes ran without a confirmation, or with one that defaulted to Yes. Configuration had the same problem: config.toml beat environment variables for some settings and not for others.
v3 gives every command the same rules. Commands run locally unless you say otherwise, ask before any hosted change, and read every setting in one order. Defaults like these can only change in a major version, so v3 changes them together.
Who is affected
Anyone who runs the CLI in CI, in deploy scripts, or through an AI coding agent. Hosted changes that run unattended now need --yes, and database commands need --remote to reach your hosted project.
Projects created with supabase init before v2.108.0. Their supabase/config.toml has an [inbucket] section, so supabase start, stop, status, and the db commands fail until you rename it.
Projects that deploy with [remotes.] blocks and also set SUPABASE_* environment variables. The variables now take precedence over the block, and config push pushes them.
Projects that edit supabase/schemas and then run db diff. Under pg-delta, use supabase db schema declarative sync instead.
Scripts that call removed commands or flags, or call supabase-go directly.
v3 changes the CLI only. Hosted projects, their data, and self-hosted Supabase are not affected.
What happens if you take no action
Nothing changes until you install v3. A pipeline that installs the latest CLI without pinning a version already runs v3. The most common failures are:
- supabase start fails with [inbucket] in supabase/config.toml is no longer supported.
- functions deploy, secrets set, config push, and db push fail in CI with HostedMutationConsentRequiredError.
- db push without --remote targets the local stack. It fails when no local stack is running. If your job started one, it succeeds there and never reaches your hosted project.
Migration steps
Update to the latest v2 release and run your usual workflows, including CI. v2.122.0 and later warn about removed commands, flags, and config keys, and about commands whose default target changes in v3. Fix each warning.
Rename [inbucket] to [local_smtp] in supabase/config.toml, along with any [remotes..inbucket] block. The keys inside don't change. v2.108.0 and later already read [local_smtp], so you can do this before you upgrade.
Add --remote to every command that should reach your hosted project, and --yes to every hosted change that runs unattended. The quick reference for CI maps common v2 commands to their v3 form.
If you use [remotes.] blocks, check the SUPABASE_* variables in CI and in your env files. Run supabase config diff before your first config push on v3.
If supabase/config.toml has no project_id, run supabase stop before you upgrade. Local container and volume names can change in v3.
Install v3 and work through the rest of the migration guide.
To upgrade later, pin v2 with npm install [email protected] --save-dev, brew install supabase/tap/supabase@2, scoop install supabase-v2-stable, or version: v2.stable on supabase/setup-cli@v3.
Rollout timeline
Date Milestone User action 2026-11-02 v3.0.0 released. npm, Scoop, the Linux packages, and supabase/setup-cli install v3 by default. v2.122.1 adds the v2.stable channels. Follow the migration steps, or pin v2 2026-11-03 brew install supabase installs v3 Same as above Ongoing v2 receives security fixes and fixes for broken behavior, but no new features Upgrade to v3 to get new featuresIf v3 breaks a workflow the migration guide doesn't cover, run supabase issue bug or open an issue.
Original source Similar to Supabase with recent updates:
- Anthropic release notes960 release notes · Latest Nov 17, 2026
- Perplexity release notes33 release notes · Latest Nov 6, 2026
- Cursor release notes144 release notes · Latest Nov 6, 2026
- Obsidian release notes125 release notes · Latest Nov 12, 2026
- xAI release notes305 release notes · Latest Nov 5, 2026
- OpenAI release notes1244 release notes · Latest Nov 16, 2026
- Oct 30, 2026
- Date parsed from source:Oct 30, 2026
- First seen by Releasebot:Nov 11, 2026
Upgrade Postgres to fix local time for Vancouver, Edmonton, and Casablanca
Supabase fixes incorrect local times for several time zones in Postgres with upgraded versions.
Older Supabase Postgres versions return wrong local times for America/Vancouver, America/Edmonton, and Africa/Casablanca. Upgrade to 15.19.0.003 or 17.11.0.003 or later to fix it.
Original source - Oct 30, 2026
- Date parsed from source:Oct 30, 2026
- First seen by Releasebot:Nov 2, 2026
Upgrade Postgres to fix local time for Vancouver, Edmonton, and Casablanca
Supabase fixes incorrect local-time conversions for Vancouver, Edmonton, and Casablanca by updating tzdata in supported Postgres versions. A project upgrade applies the fix, though it may cause downtime and some indexes may need rebuilding.
Some older Supabase Postgres versions ship an outdated tzdata package. As a result, local-time conversions such as AT TIME ZONE 'America/Vancouver' return incorrect results for three zones that changed their rules in 2026:
- British Columbia, Canada (America/Vancouver): changed on March 8, 2026.
- Morocco (Africa/Casablanca): changed on September 20, 2026.
- Alberta, Canada (America/Edmonton): changes on November 1, 2026.
This issue affects projects that use one of these zones and run a version earlier than 15.19.0.003 (Postgres 15) or 17.11.0.003 (Postgres 17). Versions 15.19.0.003 and 17.11.0.003 include the updated tzdata package.
Your stored data and timestamps are not affected. Only the conversion to local time for these zones is wrong.
How to check and fix your projects
You can find your version under Service Version in Project Settings > General and upgrade from there to get the fix. The upgrade causes downtime, so plan it for a low-traffic window. Some indexes might need a rebuild after the upgrade.
For full instructions, refer to Wrong local time for Vancouver, Edmonton, and Casablanca time zones.
Original source - Oct 23, 2026
- Date parsed from source:Oct 23, 2026
- First seen by Releasebot:Nov 12, 2026
[Public Beta] Supabase Knowledge Base
Supabase launches its Knowledge Base in public beta, offering troubleshooting and migration guides for developers and their agents.
The Supabase Knowledge Base is live in public beta at supabase.com/kb. It hosts troubleshooting and migration guides for developers and their agents.
Original source - Oct 23, 2026
- Date parsed from source:Oct 23, 2026
- First seen by Releasebot:Oct 23, 2026
[Public Beta] Supabase Knowledge Base
Supabase launches an open-source Knowledge Base with troubleshooting and migration guides for common errors and moves from other platforms.
The Supabase Knowledge Base is a new home for applied guides: how to fix a specific error, how to move to Supabase from another platform, and how to build a specific scenario.
We're launching with two types of content:
- Troubleshooting guides, now hosted on /kb at supabase.com/kb/topics/troubleshooting.
- Migration guides for moving to Supabase from Amazon RDS, Auth0, Firebase, Heroku, MySQL, Neon, Render, and more.
The knowledge base is open source and its source lives in the supabase/supabase repo for anyone to contribute to.
Original source - Oct 14, 2026
- Date parsed from source:Oct 14, 2026
- First seen by Releasebot:Nov 5, 2026
OpenTelemetry traces and metrics in the Supabase .NET SDK
Supabase adds OpenTelemetry traces and metrics across its .NET SDK for Auth, PostgREST, Storage, and Functions.
The .NET SDK now emits traces and metrics for Auth, Postgrest, Storage, and Functions. Collect them with OpenTelemetry and export to any observability backend.
Original source - Oct 14, 2026
- Date parsed from source:Oct 14, 2026
- First seen by Releasebot:Oct 14, 2026
OpenTelemetry traces and metrics in the Supabase .NET SDK
Supabase .NET SDK 8.0 adds opt-in traces and metrics for Auth, Postgrest, Storage, and Functions clients, helping developers monitor requests, operations, and failures without adding an OpenTelemetry dependency to the SDK.
What's new
The .NET SDK emit traces and metrics through System.Diagnostics. Each client exposes its own ActivitySource and Meter, so you subscribe to them the same way you subscribe to any other .NET instrumentation. The SDK takes no dependency on the OpenTelemetry packages, and the clients stay silent until something subscribes, so there is no overhead when you are not collecting.
This covers the Auth, Postgrest, Storage, and Functions clients. Realtime is not yet instrumented. URLs are recorded with the query string stripped, and no token, credential, or payload is placed in a tag.
What you get
Client Spans Metrics Postgrest One per request ({METHOD} {path}), with a db.operation tag (select, insert, update, upsert, delete, count, rpc) to tell apart operations that share an HTTP verb supabase.postgrest.http.request.duration Auth One per operation (gotrue.sign_in, gotrue.refresh_token, …), with a child span for the HTTP call supabase.gotrue.http.request.duration Storage One per request, with a storage.transfer.direction tag on uploads and downloads; a resumable (TUS) upload is a single span for the whole transfer supabase.storage.http.request.duration, supabase.storage.transfer.duration, supabase.storage.transfer.size Functions One per invocation, with a faas.invoked_name tag; a relay error is a failed span even when the HTTP status succeeds supabase.functions.invoke.durationHow to use it
Add the OpenTelemetry hosting package and an exporter alongside the SDK:
<PackageReference Include = "Supabase" Version = "8.0.0" /> <PackageReference Include = "OpenTelemetry.Extensions.Hosting" Version = "1.19.1" /> <PackageReference Include = "OpenTelemetry.Exporter.OpenTelemetryProtocol" Version = "1.19.1" />Then register the Supabase sources. Each client shares one name between its ActivitySource and its Meter, so you can register them all at once with SupabaseDiagnostics.SourceNames, or one client at a time by its own SourceName:
using OpenTelemetry.Metrics; using OpenTelemetry.Trace; using Supabase; using Supabase.Postgrest; using Supabase.Gotrue; using Supabase.Storage; using Supabase.Functions; builder.Services.AddOpenTelemetry() // All sources at once. .WithTracing(tracing => .AddSource(SupabaseDiagnostics.SourceNames.ToArray()) .AddOtlpExporter()) // Or one client at a time. .WithMetrics(metrics => .AddMeter(PostgrestDiagnostics.SourceName) .AddMeter(GotrueDiagnostics.SourceName) .AddMeter(StorageDiagnostics.SourceName) .AddMeter(FunctionsDiagnostics.SourceName) .AddOtlpExporter());Swap AddOtlpExporter for AddConsoleExporter to print locally, or use any other exporter. Without the OpenTelemetry SDK, a raw ActivityListener or MeterListener works too. We have one README per-package which shows how to do it.
Why it matters
You get the SDK's calls in the same traces as the rest of your app: which ran, how long they took, whether they failed. You write no instrumentation for it, and the SDK pulls in no OpenTelemetry dependency of its own.
Original source - Oct 12, 2026
- Date parsed from source:Oct 12, 2026
- First seen by Releasebot:Nov 5, 2026
ASP.NET Core dependency injection for the Supabase .NET SDK
Supabase adds an ASP.NET Core dependency injection package to its .NET SDK, simplifying registration of the main client and sub-clients.
The .NET SDK now ships an ASP.NET Core dependency injection package. A single method registers the main client and all sub-clients, so you don't have to wire it up by hand.
Original source - Oct 12, 2026
- Date parsed from source:Oct 12, 2026
- First seen by Releasebot:Oct 13, 2026
An outdated subset of TLS 1.2 ciphers will be disabled on project HTTP APIs
Supabase plans to retire four outdated TLS 1.2 cipher suites from its HTTP APIs starting November 10, 2026, to improve security. Most users should see no impact, but clients on unsupported systems may need updated operating systems or TLS libraries.
What is being deprecated
Most users won't notice any change. Starting November 10, 2026 at the earliest, Supabase will stop offering some outdated TLS configurations on project HTTP APIs (
<ref>.supabase.coand custom domains). Users on old, unsupported operating systems, or embedded devices that haven't been updated, may lose access if their device only supports the configurations being removed.The configurations being removed are four CBC-mode TLS 1.2 cipher suites. Cipher suites determine how a connection is encrypted. These older suites have known security weaknesses and often trigger warnings in security scans. We plan to stop offering these ciphers on TLS 1.2:
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (ECDHE-ECDSA-AES128-SHA256)
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (ECDHE-RSA-AES128-SHA256)
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (ECDHE-ECDSA-AES256-SHA384)
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (ECDHE-RSA-AES256-SHA384)
Supabase has only supported TLS 1.2 and 1.3 for several years. There is no change for TLS 1.3.
Auth, the Data API, Storage, Realtime, and Edge Functions are all sub-routes of the Supabase HTTP API, so all five are affected. Direct Postgres connections, pooler connections, and the Management API are not.
Timeline
Date Milestone October 12, 2026 Deprecation notice published October 14, 2026 Affected customers notified by email November 10, 2026 at the earliest CBC-mode ciphers removedOwners of projects that received connections using these deprecated ciphers are being contacted directly with details about the potential impact to their project. If you have any concerns about the impact to your project, please open a support ticket.
What to migrate to
In the past 30 days, fewer than 0.0001% of connections to Supabase projects negotiated these ciphers, so we expect little to no impact. Devices that only support them are running end-of-life software, such as old operating system installations or embedded products that no longer get updates.
The ciphers offered on TLS 1.2 going forward are:
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (ECDHE-ECDSA-AES128-GCM-SHA256)
- TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (ECDHE-ECDSA-CHACHA20-POLY1305)
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ECDHE-RSA-AES128-GCM-SHA256)
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (ECDHE-RSA-CHACHA20-POLY1305)
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (ECDHE-ECDSA-AES256-GCM-SHA384)
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (ECDHE-RSA-AES256-GCM-SHA384)
Migration steps
- Find any client that connects to your project over HTTPS and runs on an end-of-life operating system, an old browser, or an embedded device.
- Update that client's operating system or TLS library to a supported version so it supports at least one of the ciphers listed above, or TLS 1.3. Your preferred AI agent or the community around your tech stack may be able to help.
- If you're concerned about the impact on your users or need help preparing, open a support ticket and tell us which client and ciphers it needs.
Read more in the TLS docs.
Original source - Oct 12, 2026
- Date parsed from source:Oct 12, 2026
- First seen by Releasebot:Oct 13, 2026
ASP.NET Core dependency injection for the Supabase .NET SDK
Supabase adds a .NET dependency injection package that registers its client and sub-clients with scoped lifecycles, making SDK setup easier and reducing application boilerplate.
What's new
Supabase.Extensions.DependencyInjection is a new package that provides an easier way to plug the Supabase .NET SDK into your application. It exposes a new method on IServiceCollection called AddSupabase which registers the main client and all sub-clients:
builder.Services.AddSupabase( supabaseUrl: "https://xyz.supabase.co", supabaseKey: builder.Configuration["Supabase:Key"]!, configureOptions: options => { options.AutoConnectRealtime = true; options.PostgrestRetry = new RetryOptions { MaxRetries = 3 }; });It registers all clients (Supabase.Client, IGotrueClient, IPostgrestClient, IStorageClient, IFunctionsClient, IRealtimeClient) with a scoped lifecycle, so you can resolve them wherever you need them:
app.MapGet("/movies", async (IPostgrestClient postgrest) => await postgrest.Table<Movie>().Get());The package is available on NuGet:
dotnet add package Supabase.Extensions.DependencyInjectionWhy it matters
You can always register all the required clients in IServiceCollection yourself. This package simply does it all for you and removes boilerplate from your codebase.
Original source - Oct 9, 2026
- Date parsed from source:Oct 9, 2026
- First seen by Releasebot:Oct 14, 2026
The Supabase .NET SDK is now officially supported
Supabase officially supports its .NET SDK, recommending it for building across ASP.NET, Blazor, MAUI, Unity, Azure, and other platforms.
The .NET SDK for Supabase is now officially supported. It's the recommended way to build on Supabase from any .NET platform: ASP.NET, Blazor, MAUI, Unity, Azure, and more.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.