Supabase Auth

This patch release primarily addresses an issue in the auth module where local sessions were not being cleared during signout failures.

This canary release primarily addresses a bug in the auth module where local sessions were not being cleared during signout failures.

This patch release addresses minor issues in auth and realtime modules, specifically concerning initialization notifications and heartbeat status reporting.

This canary release addresses two minor bugs related to initialization timing in Auth and status handling in Realtime subscriptions.

This release drops support for Node.js 20, requiring users to upgrade their runtime environment to Node.js 21 or newer.

This canary release primarily removes support for Node.js 20.

This release introduces new filtering capabilities for Realtime Postgres changes and exposes cache purging in Storage. Several minor fixes address Content-Type handling in Functions and dependency pinning in Realtime.

This was a version bump only, there were no code changes.

This canary release primarily addresses two bug fixes: ensuring Content-Type overrides are respected in functions and maintaining default sorting behavior in storage list operations.

This canary release primarily addresses dependency management by pinning specific dependencies within the realtime module.

This patch release focuses on stability fixes, specifically addressing session preservation during auth failures and clarifying realtime error messages.

This was a version bump only, there were no code changes.

This beta release focuses on stability fixes, specifically addressing session handling during auth refresh failures and clarifying realtime error messages.

This canary release primarily addresses a clarification for a 404 error and server migration note within the realtime module.

This was a version bump only, there were no code changes.

This canary release primarily focuses on restoring and enabling JSR publish flags for beta testing.

This beta release primarily focuses on fixing authentication session handling during refresh failures and stabilizing the release process by pinning Deno and adjusting JSR publishing flags.

This canary release addresses an issue by pinning Deno and bounding JSR publish to prevent stranded-task hangs.

This beta release focuses on stability fixes, specifically addressing session preservation during authentication failures and improving the reliability of the release process.

This canary release addresses a bug in the authentication module related to session handling during refresh failures.

This patch release primarily addresses CI configuration and fixes a typing issue within the Postgrest module.

This was a version bump only, there were no code changes.

This canary release primarily addresses a typing issue within the postgrest module.

This canary release primarily addresses a CI configuration issue by forwarding the DOGFOOD_APP_CLIENT_ID environment variable.

This release introduces a consistent confirmation flow for auth.resend() and improves compatibility for request headers in postgrest operations.

This canary release introduces a consistent confirmation flow for auth.resend() and fixes issues related to error logging and header passing for React Native compatibility.

This release updates authentication mechanisms, enhances Realtime payload handling, and refines error reporting in Postgrest. It also updates the X-Client-Info header format.

This was a version bump only, there were no code changes.

This canary release primarily addresses an internal publishing fix related to the gotrue-js legacy mirror.

This beta release introduces structured metadata for X-Client-Info, allows binary payloads in Realtime httpSend, and fixes several authentication and Postgrest error handling issues.

This canary release primarily addresses an internal dependency pinning issue related to JSR publishing.

This beta release introduces a new structured metadata format for X-Client-Info, allows binary payloads in realtime httpSend, and fixes several authentication and PostgREST error handling issues.

This was a version bump only, there were no code changes.

This canary release reverts a previous fix related to encoding client-id in oauth requests.

This canary release introduces a significant change to the authentication system by replacing the navigator.locks-based mutex with a commit guard and dispose() mechanism.

This canary release introduces the ability to send binary payloads via httpSend in realtime and updates the X-Client-Info header format for better metadata reporting.

This canary release primarily addresses a bug in Postgrest handling of non-JSON bodies in successful responses.

This was a version bump only, there were no code changes.

This canary release fixes an issue in the Auth module where expired JWTs were not correctly resulting in an AuthInvalidJwtError from getClaims.

This release was a version bump only, containing no functional code changes.

This release was solely a version bump with no accompanying code changes.

This patch release fixes an issue with the auth signup response and improves compatibility for React Native environments using Hermes.

This was a version bump only, there were no code changes.

This canary release primarily focuses on fixing an issue with the auth signup user response and improving compatibility for React Native environments.

This release was a version bump only, containing no functional code changes.

This release was solely a version bump with no accompanying code changes.

This patch release fixes an issue with client-id encoding in OAuth requests and hides dynamic imports from hermesc.

This canary release primarily addresses an internal issue by hiding a dynamic import from hermesc.

This beta release primarily focuses on bug fixes, including ensuring the client-id is encoded in OAuth requests and resolving an OpenTelemetry import issue.

This canary release fixes an issue where the client-id was not being encoded correctly in OAuth requests.

This patch release primarily focuses on bug fixes, including correctly encoding the client-id in OAuth requests and resolving an OpenTelemetry import issue.

This beta release primarily focuses on minor fixes, including resolving an issue with OpenTelemetry imports.

This beta release (2.106.1-beta.0) primarily addresses an OpenTelemetry import issue and includes the addition of new tests.

This release introduces W3C/OpenTelemetry trace context propagation for Supabase and includes several fixes related to auth verification and storage stream handling.

This release was solely a version bump with no accompanying code changes.

This release was solely a version bump with no accompanying code changes.

This release was solely a version bump with no accompanying code changes.

This beta release introduces W3C/OpenTelemetry trace context propagation for Supabase operations and addresses internal packaging for the tracing module.

This canary release primarily focuses on internal maintenance by marking the @supabase/tracing package as private and snapshotting it for JSR.

This beta release introduces W3C/OpenTelemetry trace context propagation support for Supabase and addresses internal packaging for the tracing module.

This canary release introduces W3C/OpenTelemetry trace context propagation support for Supabase operations.

This release (2.105.5-beta.8) was strictly a version bump with no accompanying code changes.

This release was a version bump only, containing no functional code changes.

This was a version bump only, there were no code changes.

This beta release introduces significant new features including WebAuthn passkey support in Auth and deferred disconnect in Realtime. It also includes several bug fixes, notably ensuring consistent error wrapping in Postgrest and changing the behavior of the Storage exists method.

This patch release focuses on stability fixes across Auth, Postgrest, and Realtime modules, addressing issues related to JSON parsing, fetch abort detection, and storage access.

This was a version bump only, there were no code changes.

This was a version bump only, there were no code changes.

This release primarily focuses on a bug fix related to accessing sessionStorage in restricted-storage browsers within the realtime functionality.

This canary release primarily addresses a bug related to accessing sessionStorage in restricted-storage browsers within the realtime functionality.

This canary release primarily addresses bug fixes in the auth and postgrest modules, specifically handling JSON parsing failures and abort detection in fetch operations.

This release primarily addresses a bug in the auth module where getItemAsync failed on JSON parse errors, now correctly returning null.

This release primarily focuses on fixing an issue in the postgrest fetch catch mechanism related to abort detection.

This patch release primarily addresses a type-checking issue within the authentication module.

This release focuses on fixing type-checking issues related to OAuth and CustomProvider authentication types.

This was a version bump only, there were no code changes.

This patch release focuses on bug fixes, including improvements to authentication timeout forwarding, JSON serialization for WebAuthnError, and unification of Postgrest insert/upsert signatures.

This was a version bump only, there were no code changes.

This was a version bump only, there were no code changes.

This was a version bump only, there were no code changes.

This was a version bump only, there were no code changes.

This canary release focuses on minor fixes, including improving JSON serialization for WebAuthnError and unifying PostgREST insert/upsert signatures.

This release primarily focuses on a bug fix related to JSON serialization for WebAuthnError.

This release primarily focuses on a bug fix related to forwarding the lockAcquireTimeout setting within the authentication module.

This canary release primarily fixes an issue by forwarding the lockAcquireTimeout setting to the SupabaseAuthClient.

This release focuses on internal cleanup by reducing 'any' usage and standardizing the Postgrest insert/upsert API signatures.

This release primarily focuses on improving error handling within the postgrest client by ensuring all processResponse errors are wrapped in PostgrestError instances, which constitutes a breaking change for error handling logic.

This canary release primarily addresses a fix related to widening enum-like unions for better forward compatibility.

This was a version bump only, there were no code changes.

This release introduces a significant change in the Storage `exists` method behavior, preventing errors when files are not found, and improves Realtime error surfacing and enum compatibility.

This patch release addresses regressions in postgrest query handling and improves error surfacing for realtime transport issues.

This canary release primarily addresses a bug in the realtime module by correctly surfacing transport-level errors.

This release focuses on a bug fix within the realtime transport layer to correctly surface errors.