what stackpulse tracks
Better Auth releases from GitHub
StackPulse watches Better Auth release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
The most comprehensive authentication framework for TypeScript StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Better Auth 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 introduces new features like banned user messaging and Vercel BotID captcha support, along with several bug fixes across various adapters and core functionalities.
Users relying on authentication flows, especially those using banned user messaging or Vercel BotID captcha, are affected.
Update to v1.7.6 to benefit from new features and bug fixes.
This release introduces support for `database.schemaName` in PostgreSQL connections across multiple packages and fixes several bugs related to database migrations, logging, and dependencies.
Users leveraging PostgreSQL connections or affected by the fixed bugs will benefit from this release.
Update to v1.7.5 to take advantage of the new PostgreSQL schema support and bug fixes.
This release primarily fixes database option type inference for projects not using Cloudflare Workers.
Projects not using Cloudflare Workers are affected by the database option type inference fix.
Update to v1.6.33 if you are experiencing issues with database option type inference.
This release primarily includes a bug fix for improved diagnostics when Cloudflare Turnstile verification fails.
Users experiencing Cloudflare Turnstile verification issues may see improved diagnostics.
This release introduces experimental OpenTelemetry instrumentation control, adds Vitest 5 support, and fixes several bugs related to session data storage and bundling.
Developers using OpenTelemetry, Vitest, or Expo SecureStore may be affected by these changes.
Update to v1.7.4 to benefit from new features and bug fixes.
This release introduces an option to disable OpenTelemetry span creation for individual auth instances, providing more control over telemetry data collection.
Users who require fine-grained control over OpenTelemetry span creation in their auth instances are affected.
Review the new option to disable OpenTelemetry span creation if telemetry data collection needs to be managed more precisely.
This release focuses on restoring compatibility with the 1.6 account schema to avoid disruptive backfills, introduces Cloudflare as a built-in social provider, and enhances schema validation during initialization. Several bug fixes and performance improvements are also included.
Users upgrading from versions 1.7.0–1.7.2 are affected by schema changes.
Follow the upgrade guide if you applied the 1.7 issuer schema.
This release focuses on bug fixes and improvements across multiple packages, including better validation of callback and redirect URLs, fixes for Cloudflare Workers, and performance enhancements.
Users relying on URL validation, Cloudflare Workers, or performance-sensitive operations may be affected.
Update to v1.7.2 to benefit from bug fixes and improvements.
This release focuses on bug fixes across multiple packages, including improvements to database transaction support, SCIM interoperability, SAML assertion verification, and CLI behavior.
Developers using PostgreSQL, MySQL, SCIM, SAML, or the CLI may need to update their implementations to benefit from these fixes.
Update to v1.7.1 to ensure compatibility and leverage the latest bug fixes.
Better Auth 1.7 introduces significant breaking changes, including scoped accounts by issuer, wildcard endpoint matching for captcha, and OIDC back-channel logout. The release also ships MCP as its own package and models OAuth protected resources explicitly.
Developers using Better Auth with custom configurations, especially those involving joins, MCP, or OAuth provider, will be affected by these changes.
Follow the migration steps outlined in the release notes and upgrade guide to ensure compatibility with Better Auth 1.7.
This release focuses on bug fixes, particularly addressing issues with authentication context loss during cold-start requests and stricter domain verification for SSO organization assignment.
Users experiencing authentication context loss during cold-start requests or SSO organization assignment issues are affected.
Upgrade to v1.6.30 to resolve these issues.
This release candidate focuses on bug fixes, particularly for TypeScript compatibility and OAuth provider flows. Key fixes include restoring TypeScript declaration compatibility and addressing OAuth provider issues like client assertions and logout flow support.
TypeScript users and developers using OAuth provider features are affected by the fixes.
Update to this version if you are experiencing TypeScript declaration issues or OAuth provider flow problems.
This release focuses on bug fixes, including performance improvements for `deleteSessions` and stricter domain verification for SSO providers.
Users relying on SSO domain verification and `deleteSessions` functionality are affected.
Upgrade to v1.6.29 to benefit from the bug fixes.
This release primarily fixes duplicate session requests during React Suspense retries and restores TypeScript compatibility for client plugin declarations across multiple packages.
Users experiencing duplicate session requests or TypeScript compatibility issues in React Suspense, Electron, or Expo environments are affected.
Update to v1.6.28 if experiencing duplicate session requests or TypeScript compatibility issues.
This release introduces breaking changes to the OAuth device grant implementation, requiring migration to `oauthDeviceAuthorization()`. It also adds new features like disabling `displayName` and removes the `silenceWarnings` option.
Users relying on the OAuth device grant functionality are affected by the breaking change.
Follow the migration steps to update your OAuth device grant implementation before upgrading.
This release primarily focuses on bug fixes, including resolving duplicate session requests during Suspense retries and aligning CLI versions with installed packages.
Users experiencing duplicate session requests or CLI version mismatches may be affected.
Update to v1.6.27 to resolve duplicate session requests and CLI version alignment issues.
This release introduces a new placeholder email utility and fixes numerous bugs across multiple packages. The most significant change is the switch to async secure storage access in `@better-auth/expo`, which requires migration steps for custom storage implementations.
Users of `@better-auth/expo` need to update their storage implementations to handle async operations.
Update custom storage implementations in `@better-auth/expo` to handle async operations as described in the migration note.
This release primarily focuses on bug fixes, including improvements to session cleanup, OTP verification, and Redis storage operations. A new feature was added for creating stable, namespaced placeholder emails.
Users relying on session cleanup, OTP verification, or Redis storage operations may be affected by bug fixes.
Update to v1.6.26 to benefit from bug fixes and the new placeholder email utility.
This release introduces significant breaking changes, including database migrations for Microsoft account identifiers and MCP authorization alignment. It also adds new features like RP-initiated logout support and RFC 8628 device authorization grant.
Users relying on Microsoft account identifiers, MCP authorization, or device authorization flows are affected.
Perform the necessary database migrations and updates as outlined in the release notes.
This release focuses on bug fixes, particularly addressing issues with Apple OAuth, Google One Tap, and internal adapter queries. It also resolves exposure issues with `$fetch` and `$store` on the Solid client.
Users experiencing issues with Apple OAuth, Google One Tap, or Solid client functionality are affected.
Update to v1.6.25 to resolve these issues.