Skip to content

chore(deps): update dependency better-auth to v1.7.25 - #103

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/better-auth-1.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/better-auth-1.x

Conversation

@renovate

@renovate renovate Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
better-auth (source) 1.7.18 → 1.7.25 age adoption passing confidence

Release Notes

better-auth/better-auth (better-auth)

v1.7.25

Compare Source

Patch Changes

v1.7.24

Compare Source

Patch Changes

v1.7.23

Compare Source

Patch Changes

v1.7.22

Compare Source

Patch Changes

v1.7.21

Compare Source

Patch Changes
  • #​12126 4739122 Thanks @​hardikguptaofficialgit! - On Prisma with MongoDB, when your id columns use @db.ObjectId, magic link and email OTP sign-in for users with an unverified email no longer fail with a 500 (Malformed ObjectID). SAML sign-in, DPoP-bound OAuth requests, and private_key_jwt client authentication are fixed the same way, and Sign-In with Ethereum now keeps the email the user supplied instead of a placeholder. Setups with plain String id columns and other databases are unaffected.

  • #​12392 a277020 Thanks @​gustavovalverde! - Fixed the device approval page showing a valid code as invalid when the same signed-in user looked it up twice at once, such as under React Strict Mode in development.

  • #​12052 1c3410a Thanks @​lakshya-dhariwal! - If you set advanced.backgroundTasks.handler and your database adapter runs transactions (the built-in Kysely connection, MongoDB with client, or Prisma or Drizzle with transaction: true), email sign-up now keeps the database writes made while sending the verification email or running onExistingUserSignUp. Before, those writes failed because the sign-up had already been saved. With emailOTP({ overrideDefaultEmailVerification: true }), the code was never stored, so new users could not verify their email.

    Whatever adapter or background handler you use, a sign-up verification email now goes out after the new user is saved, and onExistingUserSignUp, when a duplicate sign-up triggers it, runs after the request's database work completes. If sendVerificationEmail throws, the sign-up succeeds and the error is logged; before, the sign-up failed. To reject a sign-up, use a databaseHooks.user.create.before hook. If onExistingUserSignUp throws, the error is logged and the request still returns the generic response.

  • #​12179 9105261 Thanks @​ghazy2001! - Generic OAuth providers configured with discoveryHeaders now send those headers when fetching the provider's signing keys from a jwks_uri on the same origin as discoveryUrl. Before, the keys request went out without them. Providers whose key endpoint requires the headers rejected it, so every ID token failed verification and sign-in failed. A jwks_uri on another origin still gets no headers.

    With discoveryHeaders set, the discovery request now follows redirects only within the origin of discoveryUrl, so the headers no longer reach another host. If your discoveryUrl redirects to another origin, discovery now fails and Better Auth logs an error. Set discoveryUrl to the final URL. Providers without discoveryHeaders are unaffected.

  • #​12401 c3a94c5 Thanks @​gustavovalverde! - Generic OAuth providers configured with authorizationHeaders now send those headers when refreshing an access token, not only when exchanging the authorization code. Before, a provider whose token endpoint requires one of those headers accepted the sign-in but rejected every refresh. Providers without authorizationHeaders are unaffected.

    refreshAccessToken and refreshAccessTokenRequest from @better-auth/core/oauth2 accept an optional headers input for providers that need extra headers on refresh. Client authentication headers still take precedence over it.

    Extra headers whose names differ only in case from a client authentication header, such as Authorization with authentication: "basic", no longer produce a combined, invalid header on the code exchange or refresh. Client authentication replaces them, including headers a custom tokenEndpointAuth hook sets in any casing.

  • #​12404 9b40ac6 Thanks @​bytaesu! - Plugin packages no longer import from the better-auth root, so bundlers that split code stop emitting unused Kysely chunks when used with better-auth/minimal.

  • #​12395 b0ced9d Thanks @​gustavovalverde! - On Cloudflare Workers, sign-ins with a genericOAuth provider that uses discoveryUrl, and OAuth provider requests that use a configured resource (resources), no longer hang. An auth instance created at module scope retries discovery and resource seeding on later requests. Previously, if the request running that retry ended first, every later request that needed it waited forever. Each request now retries on its own until one succeeds.

    On other runtimes, concurrent requests may send a few more discovery requests or resource lookups while the identity provider or database is unreachable.

  • #​11912 5c12074 Thanks @​gustavovalverde! - If you use PostgreSQL and other schemas in the same database are dropped while Better Auth reads the database, for example one schema per tenant or parallel test runs, the startup schema check and npx auth@latest migrate no longer fail intermittently with schema "…" does not exist or relation "…" does not exist. The startup schema check now reads only the schemas on the connection's search_path, plus any schema set with schemaName or a schema plugin, and migrate reads only the schema it migrates. Before, both read every schema in the database. If no other schemas change while Better Auth reads the database, nothing changes for you.

  • #​12403 e64f624 Thanks @​bytaesu! - SIWE verification no longer includes the internal error message (for example a database error) in its 401 response. The original error is now logged on the server instead.

  • Updated dependencies [4739122, c3a94c5, 4080630, 5c12074, b241ffc, 57fa843, 1a79da5, 2d10ae7, ef4d4f7]:

v1.7.20

Compare Source

Patch Changes

v1.7.19

Compare Source

Patch Changes
  • #​12323 a10121d Thanks @​bytaesu! - Fixed the active-sessions list in secondary storage being stored without an expiry when the last remaining session had less than a second left.

  • #​12335 c41f8ff Thanks @​bytaesu! - Fixed /admin/create-user leaving a user without a credential account when the password was rejected (for example by the Have I Been Pwned plugin), which made retrying with the same email fail with USER_ALREADY_EXISTS_USE_ANOTHER_EMAIL.

  • #​12338 e786566 Thanks @​bytaesu! - Fixed /admin/create-user leaving a user without a credential account when creating that account failed, which made retrying with the same email fail with USER_ALREADY_EXISTS_USE_ANOTHER_EMAIL.

  • #​12336 ac778b7 Thanks @​bytaesu! - Client actions now send the HTTP method passed in the second-argument fetch options, the same as when it is nested under fetchOptions. Passing a lowercase get or HEAD method no longer fails because a request body was attached.

  • #​12246 5eb69d8 Thanks @​AryaKesharwani! - /device/token now returns invalid_client instead of invalid_grant when validateClient rejects the client_id, matching /device/code and RFC 6749 section 5.2.

  • #​12319 4b0327b Thanks @​bytaesu! - Plugin schema overrides (modelName and field names) no longer leak into other instances of the same plugin in one process.

  • #​12320 2d5ef64 Thanks @​bytaesu! - Fix OAuth sign-in failing with state_mismatch during the daylight saving time fall-back hour on servers that do not run in UTC. The stored OAuth state is no longer created already expired.

  • #​12337 5f0a0fc Thanks @​bytaesu! - The OpenAPI schema now documents query parameters for endpoints whose query schema is wrapped in z.optional(), such as /get-session and Stripe's /subscription/list.

  • #​12332 89e74b8 Thanks @​bytaesu! - Fixed organization.getInvitation returning a missing, expired, or non-pending invitation error without a code. It now returns INVITATION_NOT_FOUND like the other invitation endpoints.

  • #​12318 525bd7a Thanks @​bytaesu! - Fix listMembers failing with a syntax error on PostgreSQL and MSSQL when the filter or offset matches no members.

  • #​12366 23a60a3 Thanks @​bytaesu! - Fixed SIWE sign-in leaving a user behind when creating its wallet address or account failed, which blocked that wallet from signing in again.

  • #​12340 29e45f8 Thanks @​bytaesu! - Fixed social sign-up hanging on single-connection databases when the username plugin is enabled and the provider profile maps a username.

  • Updated dependencies [8412a5f, 34ee100]:


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • Only on Thursday (* * * * 4)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/better-auth-1.x branch from 4fd0014 to dc9de18 Compare November 12, 2026 18:47
@renovate renovate Bot changed the title chore(deps): update dependency better-auth to v1.7.20 chore(deps): update dependency better-auth to v1.7.21 Nov 12, 2026
@renovate
renovate Bot force-pushed the renovate/better-auth-1.x branch from dc9de18 to 4dc383b Compare November 13, 2026 12:08
@renovate renovate Bot changed the title chore(deps): update dependency better-auth to v1.7.21 chore(deps): update dependency better-auth to v1.7.22 Nov 13, 2026
@renovate
renovate Bot force-pushed the renovate/better-auth-1.x branch from 4dc383b to 079cc5d Compare November 14, 2026 18:47
@renovate renovate Bot changed the title chore(deps): update dependency better-auth to v1.7.22 chore(deps): update dependency better-auth to v1.7.23 Nov 14, 2026
@renovate
renovate Bot force-pushed the renovate/better-auth-1.x branch from 079cc5d to f7dfb90 Compare November 15, 2026 18:11
@renovate renovate Bot changed the title chore(deps): update dependency better-auth to v1.7.23 chore(deps): update dependency better-auth to v1.7.24 Nov 15, 2026
@renovate
renovate Bot force-pushed the renovate/better-auth-1.x branch from f7dfb90 to fbecfbb Compare November 16, 2026 02:34
@renovate renovate Bot changed the title chore(deps): update dependency better-auth to v1.7.24 chore(deps): update dependency better-auth to v1.7.25 Nov 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants