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 canary release focuses on fixing issues related to PostgREST code generation and type overrides.
Developers using PostgREST code generation in Supabase JS may be affected by the fixes.
Update to this canary version if you encounter issues with PostgREST code generation.
This release focuses on improving trace context headers and propagation sampling for better diagnostics and CORS compatibility.
Users relying on trace context headers or CORS configurations may be affected.
This release focuses on improving trace context headers and propagation sampling for better diagnostics and CORS compatibility.
Developers using trace context headers or diagnostics in Supabase JS may benefit from these fixes.
This release focuses on fixing issues in the realtime module, specifically addressing duplicate bindings and stale join payloads during sign-out.
Users relying on the realtime module may experience improved stability and fewer issues with duplicate bindings or stale payloads.
Update to this version to benefit from the fixes in the realtime module.
This release focuses on fixing a realtime issue where stale join payloads were not cleared on sign-out.
Users relying on realtime functionality may be affected by stale join payloads.
Update to this version to ensure stale join payloads are cleared on sign-out.
This release focuses on fixing a bug in the realtime functionality to prevent duplicate bindings.
Users relying on realtime bindings may have experienced duplicate events, which is now fixed.
Update to this version to resolve the duplicate bindings issue.
This patch release fixes an issue with preserving 5xx error messages in auth and ensures token refresh is not disabled when using setAuth in realtime.
Users relying on 5xx error messages in auth or realtime token refresh functionality are affected.
Update to v2.112.1 to ensure proper error message handling and token refresh behavior.
This canary release fixes an issue in the realtime module where `setAuth` could inadvertently disable token refresh functionality.
Users relying on `setAuth` in the realtime module may be affected by the token refresh issue.
Update to this version to ensure token refresh functionality works correctly with `setAuth`.
This canary release includes a fix for preserving 5xx error messages in the auth module.
Developers using the auth module may be affected by changes in error message handling.
Update to this version if you rely on consistent 5xx error messages in the auth module.
This release introduces opt-in OpenTelemetry tracing and includes several fixes across auth, postgrest, storage, and supabase modules.
Developers using OpenTelemetry tracing or specific UUID validation, error handling, and storage functionalities are affected.
This canary release includes fixes for PostgREST and Storage API error handling, ensuring proper behavior in specific edge cases.
Developers using PostgREST's `maybeSingle` method or handling Storage API errors may be affected.
Update to this version if you rely on `maybeSingle` or need detailed Storage API error codes.
This canary release moves OpenTelemetry tracing to an opt-in model under a '/tracing' subpath, requiring updates for existing tracing implementations.
Developers using OpenTelemetry tracing in Supabase JS are affected as it is now opt-in under a subpath.
Update OpenTelemetry tracing usage to reference the new '/tracing' subpath if needed.
This beta release introduces opt-in OpenTelemetry tracing and fixes a database retry option forwarding issue.
Developers using OpenTelemetry tracing or database retry options are affected.
Update to this beta version to test the new tracing opt-in feature and retry option fix.
This canary release includes fixes for UUID validation in the auth module and resolves a return type mismatch in the storage module's `createSignedUrls` function.
Developers using the auth module with uppercase UUIDs or the storage module's `createSignedUrls` function may be affected.
Update to this canary release if you encounter issues with UUID validation or `createSignedUrls` return types.
This canary release includes a fix to forward the database retry option.
Developers using the database retry option in Supabase JS are affected.
Update to this version to ensure the database retry option is forwarded correctly.
This release introduces improvements to the authentication flow by storing PKCE verifiers in per-flow slots, ensuring better handling of overlapping flows.
Developers using Supabase JS for authentication flows with overlapping PKCE verifiers are affected.
Update to v2.111.0 to benefit from improved handling of overlapping authentication flows.
This release introduces improvements to the authentication system, specifically enhancing PKCE verifier storage to handle overlapping flows more effectively.
Developers using Supabase JS for authentication with overlapping flows will benefit from this update.
Update to the latest canary release to take advantage of the improved PKCE verifier handling.
This release focuses on bug fixes and security improvements, including addressing audit advisories and reducing console noise for stale refresh tokens.
Users relying on Supabase JS for authentication and real-time functionality may benefit from reduced console noise and improved security.
Update to v2.110.9 to benefit from security fixes and improvements.