v1.6.25
This release fixes Apple OAuth PKCE code challenge not being sent during authorization, Google One Tap incorrectly creating users when sign-up was disabled, Solid client missing $fetch and $store exposure, and internal adapter queries being routed to wrong tables when model names were remapped.
better-auth
Bug Fixes
- Fixed Apple OAuth not sending the PKCE code challenge during authorization, causing token exchange failures (#10294)
- Fixed Google One Tap creating new users when sign-up was disabled on the Google provider (#10479)
- Fixed
$fetchand$storenot being exposed on the Solid client (#10444) - Fixed internal adapter queries being routed to the wrong table when a built-in table's
modelNamewas set to another table's schema key (e.g.user.modelName = "account").
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
@birkskyum, @jsj, @krish-vachhani
Full changelog: v1.6.24...v1.6.25
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.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.
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.