Supabase JS

This patch release fixes 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 auth initialization timing and realtime heartbeat status reporting.

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

This canary release primarily removes support for Node.js 20, requiring users to upgrade their runtime environment.

This release introduces new filtering and cache purging capabilities for Realtime and Storage, alongside improvements to Auth admin APIs and bug fixes across Functions and Realtime dependencies.

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

This canary release primarily addresses bug fixes related to Content-Type overrides in functions and default sorting behavior in storage list operations.

This canary release primarily addresses dependency pinning for the realtime module to ensure stability.

This patch release focuses on stability fixes, particularly preserving user sessions during authentication refresh 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 preservation during auth refresh failures and clarifying realtime error messages.

This canary release primarily addresses a clarification for the httpSend() 404 error and server migration note within the realtime functionality.

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 focuses on stability fixes, specifically addressing session preservation during authentication failures and improving the release process reliability by pinning Deno and adjusting JSR publishing settings.

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 release process stability.

This canary release primarily addresses a bug in the authentication flow, ensuring valid sessions are preserved during refresh failures.

This patch release addresses minor fixes in CI configuration and Postgrest typing.

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 resolves issues related to error logging and header passing for custom fetch environments.

This canary release introduces a consistent confirmation flow for auth.resend() and fixes issues related to error logging and header passing for RN/custom-fetch compatibility.

This release updates authentication mechanisms, enhances Realtime payload handling, and refines error reporting in Postgrest. It also addresses several authentication flow issues.

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 a new structured metadata format for X-Client-Info and updates authentication handling by removing the navigator.locks-based mutex. Several bug fixes address JWT validation and error handling in Auth and Postgrest modules.

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

This beta release introduces new features for authentication mutex handling, binary payload support in realtime, and structured metadata for client info. Several fixes address JWT handling, OAuth redirects, and error reporting in PostgREST responses.

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 tracking.

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

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

This canary release fixes an issue where expired JWTs were not correctly returning 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 addresses an authentication bug by ensuring the client-id is encoded in OAuth requests and resolves an OpenTelemetry import issue.

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

This beta release 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 a version bump only, containing no functional 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 for Supabase and includes internal packaging fixes 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 errors are consistently wrapped as PostgrestError and modifying the Storage 'exists' behavior.

This patch release focuses on stability fixes across Auth, Postgrest, and Realtime modules, addressing JSON parsing errors, fetch abort detection, and storage access in restricted environments.

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

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

This release primarily addresses a bug fix related to sessionStorage access 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 module.

This canary release addresses minor bugs in the auth and postgrest modules, specifically handling JSON parse 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 configurations.

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

This patch release focuses on stability and internal improvements, including unifying Postgrest signatures and enhancing serialization for auth errors.

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 client.

This canary release primarily addresses a bug by forwarding the lockAcquireTimeout setting to the SupabaseAuthClient.

This release focuses on internal improvements, specifically reducing 'any' usage and unifying Postgrest insert/upsert signatures.

This release primarily focuses on improving error handling within the Postgrest client by ensuring all processResponse errors are wrapped in a PostgrestError instance, 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 general forward compatibility.

This patch release addresses a query reassignment regression in postgrest and improves error surfacing for transport-level CHANNEL_ERROR in realtime.

This canary release primarily fixes an issue where real errors were not being surfaced correctly at the transport level for realtime channels.

This release focuses on a bug fix within the realtime transport layer, ensuring proper error surfacing.