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