[dependabot]

Bumps @better-auth/drizzle-adapter from 1.6.33 to 1.7.7.

Release notes

Sourced from @​better-auth/drizzle-adapter's releases.

v1.7.7

better-auth

Magic Link upgrade: Upgrade servers sharing verification storage together, request new Magic Links, and restart pending OAuth/SAML sign-ins. No database migration is required. See the critical advisory for affected configurations and custom storage changes.

Bug Fixes

• Fixed a critical Magic Link account-takeover vulnerability. (#11494)
• Fixed ID-token sign-in ignoring the social provider’s disableSignUp setting. (#11491)
• Fixed OAuth Proxy accepting sign-in state as a provider profile. (#11494) Upgrade all OAuth Proxy participants together; see the OAuth Proxy upgrade guidance.
• Fixed CAPTCHA errors missing the JSON Content-Type header. (#11476)
• Fixed the active organization failing to refresh after sign-in when a session hook selects the initial organization. (#11375)
• Fixed rate-limit errors missing the JSON Content-Type header. (#11469)

For detailed changes, see CHANGELOG

@better-auth/oauth-provider

Features

• Added optional validateRedirectUri validation for trusted deployments with dynamic OAuth redirect URIs. (#8686)
• Added verifyOAuthQueryParams to verify signed authorization queries before rendering a custom consent page. (#11402)

For detailed changes, see CHANGELOG

@better-auth/drizzle-adapter

Bug Fixes

• Fixed concurrent PostgreSQL requests exceeding database-backed rate limits. (#11331)

For detailed changes, see CHANGELOG

@better-auth/kysely-adapter

Bug Fixes

• Fixed consumeOne deleting a record after a concurrent write invalidates its original condition. (#11495)

For detailed changes, see CHANGELOG

Contributors

Thanks to everyone who contributed to this release:

@​aryan1306, @​bytaesu, @​gitmotion, @​gustavovalverde, @​lennondotw

Full changelog: v1.7.6...v1.7.7

... (truncated)

Changelog

Sourced from @​better-auth/drizzle-adapter's changelog.

1.7.7

Patch Changes

• #11331 35d7cd3 Thanks @​gitmotion! - Drizzle incrementOne now rejects updates when a concurrent write makes the original where condition false. This prevents stale updates and counter limits from being exceeded on PostgreSQL. Both the default adapter and relations-v2 retain the single-row limit.

1.7.6

Patch Changes

• #11333 631ac29 Thanks @​bytaesu! - Preserve logical model identity when a custom model name matches another schema key.

1.7.5

Patch Changes

• #11263 e18bc83 Thanks @​bytaesu! - Defer Drizzle relation metadata access until a relational query runs, preserving lazy database initialization during application builds.

1.7.4

Patch Changes

• #11213 b905bfe Thanks @​bytaesu! - Run schema validation for the Drizzle Relations v2 adapter, including configurations that provide only relations, so schema mismatches are reported during initialization.

1.7.3

Patch Changes

• #11179 352d012 Thanks @​bytaesu! - Validate Drizzle schema objects and generated Prisma client models during initialization, including in production, and report mismatches with guidance for fixing them. These checks do not query the database and cannot detect unapplied migrations.

  For Prisma clients whose model metadata omits nullability, auth generate reports required fields that Better Auth never writes by reading the existing Prisma schema. Set advanced.database.validateSchema: false to disable runtime validation.

1.7.2

Patch Changes

• #10859 ea77118 Thanks @​bytaesu! - Reject missing Drizzle schema fields before building compound where clauses, preventing malformed SQL when an application schema is out of date.

• #10941 5aea9f7 Thanks @​bytaesu! - Prevent one-to-one joins from failing in Drizzle Relations v1 and v2 when usePlural is enabled. Resolve generated and legacy relation keys from Drizzle runtime metadata, including Relations v2 setups without an adapter schema.

1.7.1

1.7.0

Minor Changes

• #10402 763a267 Thanks @​gustavovalverde! - Plugin database schemas can now define named or generated table-level indexes across multiple fields. SQL migrations and generated Drizzle or Prisma schemas resolve configured table and column names consistently, while the MongoDB adapter creates the same indexes before the first index-enforcing write.

• #7169 5d38b13 Thanks @​ping-maxwell! - Add a schemaName option to the Drizzle Relations v2 adapter config. When set on PostgreSQL, schema generation now emits a pgSchema("...") namespace and uses namespaced table definitions (for example, authSchema.user(...)), matching the v1 CLI generator behavior.

... (truncated)

Commits

• db02f23 chore: release v1.7.7 (#11413)
• 35d7cd3 fix(drizzle-adapter): re-check the incrementOne guard on the UPDATE (#11331)
• 229a02a chore: release v1.7.6 (#11322)
• dcaa5a7 feat(cli): add check command for schema validation (#11314)
• 631ac29 fix(db): preserve model identity across adapters (#11333)
• 5468e6b chore: release v1.7.5 (#11245)
• e18bc83 fix(drizzle-adapter): defer relation metadata access (#11263)
• 735008f chore: release v1.7.4 (#11216)
• b905bfe fix(drizzle-adapter): validate schemas in relations v2 (#11213)
• cfedf97 docs: update CLI references to auth (#11214)
• Additional commits viewable in compare view

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	67.27%	9094 / 13517
🔵	Statements	66.25%	12253 / 18493
🔵	Functions	68.08%	2935 / 4311
🔵	Branches	57.25%	5141 / 8979

File Coverage

No changed files found.

Generated in workflow #1198 for commit 624d917 by the Vitest Coverage Report Action

[dependabot]

Looks like @better-auth/drizzle-adapter is up-to-date now, so this is no longer needed.