what stackpulse tracks
Supabase JS releases from GitHub
StackPulse watches Supabase JS release notes and keeps the original source link close to every summary.
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 adds query builder options to `.from()` for configuring a custom fetch per request and introduces Realtime broadcast persistence. It also fixes issues in Auth, Realtime, and Storage, including preserving local sessions when global sign-out fails on the server.
Supabase JS users working with PostgREST requests, Realtime broadcasts, Auth sign-out, or Storage operations may benefit from the new options and fixes.
This is a version bump only; the release notes report no code changes. No features, fixes, or migration steps are described.
view details view source on github->This prerelease adds persistence for Realtime broadcasts. It also updates the unsupported serializer error to include the `vsn` value.
Users of Supabase JS Realtime broadcasts may be affected by the new persistence feature; the release notes provide no further details about its behavior.
This canary release fixes global sign-out behavior in auth. Previously, the local session was cleared even when the server failed to log out; the fix prevents that incorrect local-session change.
Applications using global sign-out are affected when the server fails to log out, as local session handling is corrected.
Upgrade to this canary release if you need the corrected global sign-out behavior.
This canary release fixes Storage uploads to ignore undefined `FileOptions`. No other changes are described in the release notes.
Users performing Storage uploads with undefined `FileOptions` are affected by this fix.
This release fixes an issue in the storage module where the `exists` method incorrectly reported invalid JWT or missing bucket errors as missing file errors.
Users relying on the `exists` method in the storage module may have experienced incorrect error reporting.
Update to this version to ensure accurate error reporting in the `exists` method.
This release fixes a bug in the `deleteUser` function where an empty object was incorrectly cast to a `User` type.
Developers using the `deleteUser` function in the auth module are affected by this bug fix.
Update to this version to resolve the `deleteUser` casting issue.
This canary release introduces the ability to customize fetch options per request in the PostgREST query builder.
Developers using the PostgREST query builder in Supabase JS are affected.
Update to this version to utilize the new fetch customization feature.
This release introduces improvements to PostgREST computed fields and storage uploads, along with patching CI-related security advisories.
Developers using PostgREST computed fields or storage uploads are affected.
Update to v2.118.0 to benefit from new features and security patches.
This is a version bump only with no code changes.
view details view source on github->This release is a version bump with no code changes.
view details view source on github->This canary release introduces improvements to PostgREST computed fields and resolves RPC overloads for type generation. It also patches security advisories related to Next.js and Sharp.
Developers using PostgREST computed fields or RPC overloads in Supabase JS are affected.
Update to this canary release to benefit from the fixes and improvements.
This patch release fixes a security vulnerability in the realtime-js example and addresses several bugs related to Blob/File handling, timeout errors, and storage multipart uploads.
Users of the realtime-js example and those sending Blob/File objects or using storage multipart uploads may be affected.
Update to v2.117.3 to receive the security patch and bug fixes.
This canary release fixes an issue with the storage functionality where multipart fields were not being sent before files.
Users of the storage functionality in Supabase JS may be affected by the fix for multipart field ordering.
Update to v2.117.3-canary.1 if you are using the storage functionality and experiencing issues with multipart field ordering.
This canary release includes a security patch for an RCE vulnerability in the realtime-js example and fixes for handling Blob/File objects in functions and timeout errors in PostgREST.
Users of the realtime-js example and those sending Blob/File objects with functions may be affected by the fixes.
Update to this version if you are using the realtime-js example or sending Blob/File objects with functions.
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.