v1.7.6
Better Auth v1.7.6 adds support for customizable banned user messages and Vercel BotID captcha provider for authentication. This release fixes critical bugs including React hydration mismatches, password length validation, overlapping auth query requests, model identity issues across multiple adapters, and OAuth social account linking.
better-auth
Features
- Added support for a
bannedUserMessagefunction that receives the banned user, allowing sign-in errors to include details such as the ban reason. (#11325) - Added Vercel BotID as a captcha provider for protected authentication routes. (#11016)
Bug Fixes
- Passwords over
maxPasswordLengthare now rejected withPASSWORD_TOO_LONGbefore hashing or verification. (#11324) - Fixed React hydration mismatches when session or plugin auth queries resolve before streamed components hydrate. (#11316)
- Prevented older auth-query responses from overwriting newer results when requests overlap. (#11376)
- Fixed model identity when a custom model name matches another schema key. (#11333)
- Fixed schema validation for Cloudflare D1 when the Kysely dialect cannot introspect the database. (#11366)
- Fixed social account linking through the OAuth Proxy plugin. (#11268)
For detailed changes, see CHANGELOG
@better-auth/kysely-adapter
Bug Fixes
- Fixed model identity when a custom model name matches another schema key. (#11333)
- Fixed schema validation for SQLite-generated primary keys, including
INTEGER PRIMARY KEYcolumns withoutAUTOINCREMENT. (#11374) - Fixed schema validation for Cloudflare D1 when the Kysely dialect cannot introspect the database. (#11366)
For detailed changes, see CHANGELOG
@better-auth/prisma-adapter
Bug Fixes
- Fixed model identity when a custom model name matches another schema key. (#11333)
- Fixed schema validation for capitalized custom Prisma model names. (#11319)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Fixed model identity when a custom model name matches another schema key. (#11333)
For detailed changes, see CHANGELOG
@better-auth/drizzle-adapter
Bug Fixes
- Fixed model identity when a custom model name matches another schema key. (#11333)
For detailed changes, see CHANGELOG
@better-auth/memory-adapter
Bug Fixes
- Fixed model identity when a custom model name matches another schema key. (#11333)
For detailed changes, see CHANGELOG
@better-auth/mongo-adapter
Bug Fixes
- Fixed model identity when a custom model name matches another schema key. (#11333)
For detailed changes, see CHANGELOG
@better-auth/stripe
Bug Fixes
- Fixed automatic seat updates after an organization resubscribes, even when canceled subscriptions remain in its history. (#11347)
For detailed changes, see CHANGELOG
auth
Features
- Added read-only
checkandcheck schemacommands to validate your configured adapter schema on demand. (#11314)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
@bytaesu, @davbrito, @rwieruch, @Smidge, @Wadiou, @XXMOHAMED012
Full changelog: v1.7.5...v1.7.6
Source: original entry ↗
More from Better Auth
Follow Better Auth to get its new changes in your feed and email digest.
Magic Link upgrade and critical security fixes
Better Auth v1.7.7 addresses a critical Magic Link account-takeover vulnerability and multiple security issues including OAuth/SAML sign-in bugs and missing JSON headers in error responses. Magic Link requires a server upgrade with verification storage coordination, but no database migration is needed.
v1.7.5 Release
This release adds database schema name support for direct PostgreSQL connections and includes multiple bug fixes across better-auth packages, including improvements to server-side logging, database migrations, index validation, and adapter initialization.
Fixed database option type inference for non-Cloudflare projects
Fixed database option type inference for projects that do not use Cloudflare Workers, improving compatibility for diverse deployment environments.