what stackpulse tracks
Supabase JS releases from GitHub
StackPulse watches Supabase JS release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Isomorphic JavaScript client for Supabase StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Supabase JS release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release fixes instantiation depth errors that could occur with large relationship unions in PostgREST queries.
Users with large relationship unions in PostgREST queries may have encountered instantiation depth errors.
Update to v2.117.2 if you experience instantiation depth errors with large relationship unions.
This canary release focuses on fixing instantiation depth errors in PostgREST when handling large relationship unions.
Developers using PostgREST with large relationship unions may be affected by instantiation depth errors.
Upgrade to this canary release to resolve instantiation depth errors.
This patch release fixes an issue where stored sessions were not properly returned when a refresh operation lost to another tab.
Users experiencing session refresh race conditions in multi-tab scenarios are affected.
Update to v2.117.1 to fix session refresh race conditions.
This canary release fixes an issue where a session refresh in one tab could lose to another tab, ensuring the stored session is returned correctly.
Users with multiple tabs open using Supabase auth may be affected by session refresh behavior.
This release enables the passkey API by default and deprecates the experimental opt-in flag. It also adds support for forwarding mediation options during passkey authentication.
Users of the experimental passkey API will need to update their code as the opt-in flag is deprecated.
Remove any explicit experimental passkey opt-in flags from your auth configuration.
This canary release enables the passkey API by default and deprecates the experimental opt-in. Users should update their code to remove explicit passkey experimental flags.
Users relying on the experimental passkey opt-in will need to migrate to the default API.
Update code to remove explicit passkey experimental flags.
This canary release adds support for forwarding mediation options in passkey authentication. The change enables more control over credential selection behavior during authentication.
Developers using passkey authentication with Supabase JS may be affected by the new mediation option.
Review the new mediation option if using passkey authentication.
This release introduces new features for Supabase JS, including MFA recovery codes API, bucket lifecycle configuration, and versionId support in storage. Several fixes address issues in auth and storage.
Developers using Supabase JS for auth and storage functionalities are affected.
This canary release introduces MFA recovery codes for authentication and versionId support for storage URL creation methods. These features enhance security and version control capabilities.
Developers using Supabase auth and storage features are affected by the new capabilities.
This canary release adds support for topk 10k in storage and removes legacy prefixes from storage lifecycles.
Users of Supabase JS storage functionality may be affected by the legacy prefix removal.
Check storage lifecycle configurations if using legacy prefixes.
This canary release includes a fix for silencing the commit-guard-discarded refresh in the initial session for the auth module.
Developers using the auth module may experience improved session handling.
This canary release adds storage bucket lifecycle configuration support. No breaking changes or security fixes are included.
Users utilizing Supabase storage buckets may benefit from the new lifecycle configuration feature.
This canary release adds a warning when schema is passed outside database options to help developers identify potential misconfigurations.
Developers passing schema outside db options may see warnings.
Review code for schema parameter usage outside db options.
This release introduces a new feature to retrieve OpenAPI specifications directly from PostgREST.
Developers using PostgREST in Supabase JS will benefit from easier access to OpenAPI specifications.
Consider using the new `getOpenApiSpec()` method for OpenAPI integration.
This release introduces a new feature to retrieve OpenAPI specifications directly from PostgREST.
Developers using PostgREST in Supabase JS may benefit from the new `getOpenApiSpec()` method.
Consider using the new `getOpenApiSpec()` method if you need to retrieve OpenAPI specifications.
This release introduces storage object versioning updates and includes important security patches for dependencies. It also fixes an auth issue with unverified factor cleanup.
Users of Supabase JS may benefit from storage versioning updates and security patches.
Update to v2.114.0 to benefit from new features and security patches.
This canary release introduces updates to object versioning in storage and includes fixes for auth and dependency security issues.
Users of Supabase JS storage and auth features may be affected by the updates and fixes.
Update to the latest version to benefit from the new features and fixes.
This release introduces a new feature in the realtime module, allowing users to wait for PostgreSQL changes.
Developers using Supabase JS for realtime PostgreSQL changes are affected.
Update to v2.113.0 to utilize the new feature for waiting on PostgreSQL changes.
This prerelease introduces a new feature in the realtime module, allowing users to wait for PostgreSQL changes.
Developers using Supabase JS for realtime PostgreSQL changes are affected.
This patch release fixes several minor issues including AbortError handling in auth when acquireTimeout is 0, deprecation warnings for the lock option, PostgREST type generation improvements, and realtime client logging fixes.
Users relying on the deprecated 'lock' option in auth or encountering AbortError with acquireTimeout set to 0 may be affected.
Update to avoid deprecated 'lock' option warnings and potential unhandled promise rejections in auth.