v1.6.23 Release
Release includes Yandex OAuth provider support, fixes for row counting in D1 and postgres-js adapters, fixes for organization subscription actions in Stripe integration, and fixes for string default value escaping in Drizzle schema generation.
better-auth
Features
- Added Yandex as a social OAuth provider (#9138)
For detailed changes, see CHANGELOG
@better-auth/drizzle-adapter
Bug Fixes
- Fixed affected row counting for D1 and postgres-js adapters (#10257)
For detailed changes, see CHANGELOG
@better-auth/stripe
Bug Fixes
- Fixed organization subscription actions (cancel, upgrade, restore, and the billing portal) that could act on the wrong organization.
For detailed changes, see CHANGELOG
auth
Bug Fixes
- Fixed string default values not being properly escaped in the generated Drizzle schema (#10259)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
Full changelog: v1.6.22...v1.6.23
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.