Repository navigation
fix(deps): update better-auth monorepo to v1.7.25 - #2906
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
SafeDep Report SummaryPackage Details
This report is generated by SafeDep GitHub App |
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
from
November 4, 2026 22:48
db05a12 to
e44ad2a
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
4 times, most recently
from
November 5, 2026 21:02
a2dd522 to
9c6f2e0
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
12 times, most recently
from
November 10, 2026 02:13
184af83 to
ab8612c
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
from
November 10, 2026 18:02
ab8612c to
ab3a435
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
3 times, most recently
from
November 11, 2026 19:01
cfab7fd to
44dfbb3
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
from
November 12, 2026 13:49
44dfbb3 to
2e7bc50
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
from
November 12, 2026 17:07
2e7bc50 to
8142532
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
7 times, most recently
from
November 13, 2026 14:29
ff8c304 to
ce5a5b1
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
12 times, most recently
from
November 14, 2026 19:19
cb51378 to
5e38400
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
7 times, most recently
from
November 16, 2026 00:58
ddd92ac to
6d4f57e
Compare
renovate
Bot
force-pushed
the
renovate/patch-better-auth-monorepo
branch
from
November 16, 2026 11:21
6d4f57e to
73e1cc6
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
1.7.16→1.7.251.7.16→1.7.251.7.16→1.7.251.7.16→1.7.251.7.16→1.7.25Release Notes
better-auth/better-auth (@better-auth/api-key)
v1.7.25Compare Source
v1.7.24Compare Source
Patch Changes
0597f4cThanks @gustavovalverde! - Official packages now accept anybetter-call1.4 patch release from 1.4.5 as a peer.v1.7.23Compare Source
v1.7.22Compare Source
v1.7.21Compare Source
Patch Changes
9b40ac6Thanks @bytaesu! - Plugin packages no longer import from thebetter-authroot, so bundlers that split code stop emitting unused Kysely chunks when used withbetter-auth/minimal.v1.7.20Compare Source
v1.7.19Compare Source
v1.7.18Compare Source
v1.7.17Compare Source
better-auth/better-auth (@better-auth/core)
v1.7.25Compare Source
Patch Changes
#12572
69e14d8Thanks @gustavovalverde! - Authorization URLs now keep the authorization endpoint's existing query text unchanged. Before, building the URL re-encoded parameters already on the endpoint, for example%20became+, which broke providers that expect the exact query they published. A parameter that Better Auth sets still replaces an endpoint parameter with the same name.#12586
2a8750bThanks @gustavovalverde! - The default in-memory DPoP replay store used byverifyAccessTokenRequestno longer slows down as traffic grows. Before, each DPoP request scanned every proof recorded in the replay window, so CPU time per request grew with the request rate.#12587
75c0821Thanks @gustavovalverde! - DPoP now works on deployments that keep verification values only in secondary storage. Before, every request with a DPoP proof to the OAuth provider, UserInfo, orrequireMcpAuthfailed with a 500 error unlessverification.storeInDatabase: truewas set. Used proofs are now recorded in secondary storage, so a replayed proof is still rejected across instances.createDpopReplayStorenow also accepts the auth context, ascreateDpopReplayStore(await auth.$context), and picks the same storage.v1.7.24Compare Source
Patch Changes
0597f4cThanks @gustavovalverde! - Official packages now accept anybetter-call1.4 patch release from 1.4.5 as a peer.v1.7.23Compare Source
Patch Changes
#12501
cfa73e9Thanks @gustavovalverde! -requireMcpAuthnow reads the signing keys from the auth instance instead of requesting its own/jwksendpoint, so MCP routes served from the same app as the auth server no longer fail with a 500 on runtimes that block requests to their own hostname, such as a single Cloudflare Worker.Set
jwksUrlto keep fetching the keys over HTTP.#12480
c10b35dThanks @gustavovalverde! - Theadvanced.database.validateSchemaJSDoc now says validation runs when the auth instance is first used, and that adapters other than Kysely, Drizzle, and Prisma skip it with a log message.v1.7.22Compare Source
Patch Changes
#12333
6536174Thanks @bytaesu! - FixgetSessionfailing with "Failed to get session" when auser.additionalFieldsentry references a table outside the Better Auth schema, including with database joins enabled on Drizzle and Prisma. Join resolution now matchesreferences.modelagainst schema keys only.#12432
262adc0Thanks @gustavovalverde! - Reject introspected access tokens that fail claim validation with a 401UNAUTHORIZEDerror. WhenremoteVerifyintrospection reported an active token whoseaud,iss,exp, ornbfclaim did not pass the configured checks,verifyBearerTokenandverifyAccessTokenRequestthrew a plainError, so resource servers answered with a 500 instead of aWWW-Authenticatechallenge. Expired tokens now reporttoken expiredand other claim failures reportinvalid access token, matching local JWKS verification.#12445
e9d8e59Thanks @gustavovalverde! - Resource-server challenges no longer turn a rejected request into a 500, and they now tell clients when the token they sent is invalid.createResourceServerChallengeused to throw when anerror_descriptioncontained a character that RFC 6750 does not allow in that parameter. Better Auth's own DPoP messageDPoP proof typ must be "dpop+jwt"was one of them. The description is now fitted into the allowed characters:"becomes', other disallowed characters become spaces, and an empty result is left out. Invalid scope tokens inchallengeScopesstill throw.When the request presented a token that failed verification, the 401 Bearer challenge now carries
error="invalid_token"and anerror_description, following RFC 6750 §3 and §3.1. A request without a token still gets no error code.verifyBearerTokenandverifyAccessTokenRequestnow seterror: "invalid_token"anderror_descriptionon their expired, invalid, inactive, and unreadable token errors, and the challenge's response body includes both fields alongsidemessage.v1.7.21Compare Source
Patch Changes
#12126
4739122Thanks @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, andprivate_key_jwtclient authentication are fixed the same way, and Sign-In with Ethereum now keeps the email the user supplied instead of a placeholder. Setups with plainStringid columns and other databases are unaffected.#12401
c3a94c5Thanks @gustavovalverde! - Generic OAuth providers configured withauthorizationHeadersnow 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 withoutauthorizationHeadersare unaffected.refreshAccessTokenandrefreshAccessTokenRequestfrom@better-auth/core/oauth2accept an optionalheadersinput 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
Authorizationwithauthentication: "basic", no longer produce a combined, invalid header on the code exchange or refresh. Client authentication replaces them, including headers a customtokenEndpointAuthhook sets in any casing.#11716
1a79da5Thanks @bytaesu! - Authentication requests no longer hang on Cloudflare Workers when the request that started schema validation ends before validation finishes. On Workers, each request now runs its own schema lookup until one completes.#12402
2d10ae7Thanks @gustavovalverde! - Withadvanced.database.generateId: "serial", filtering anidor reference field withnullnow compares it withnull. Before, thenullbecame0, soeq nullmatched no row and, on the memory adapter,ne nullalso matched rows where the field was unset.#12425
ef4d4f7Thanks @bytaesu! - Telemetry now reports Cloudflare Workers asworkerdinstead ofnodewhennodejs_compatis enabled.@better-auth/core/envexports the runtime detection it uses.v1.7.20Compare Source
Patch Changes
#11904
a3f50d0Thanks @gustavovalverde! - OAuth provider deployments served over plain HTTP on a private network, such as a LAN address, a VPN, or a private DNS name, can now accepthttpredirect URIs through the newallowInsecureRedirectUrioption. Returntruefrom it for origins you control. The same option lets web clients uselocalhostcallbacks during development. Without the option, redirect URI validation is unchanged.If your issuer (
baseURL, orjwt.issuerwhen set) useshttpon a non-loopback host, discovery and theissauthorization response parameter now report it as configured instead of rewriting it tohttps. They now match the issuer in issued tokens, so OpenID Connect sign-ins no longer fail on the mismatch. If a proxy terminates TLS in front of Better Auth, setbaseURLto the publichttpsURL.When an authorization request uses a registered
httpredirect URI that the HTTPS policy rejects, the error now appears on the server error page instead of being redirected to that URI.Client registration and updates now reject post-logout redirect URIs that contain credentials, such as
https://user:pass@example.com/logged-out, matching the existing rule for redirect URIs.v1.7.19Compare Source
Patch Changes
#12317
8412a5fThanks @bytaesu! - Failed fallback join queries are now reported only through the configured logger, instead of also printing the raw database error (including SQL and bound values) withconsole.error.#12369
34ee100Thanks @bytaesu! -getAccessTokenandrefreshTokennow fail when a provider refuses a token refresh with a 200 status, as GitHub does, instead of returning the expired access token.v1.7.18Compare Source
Patch Changes
9342a73Thanks @gustavovalverde! - Resource servers that setverifyOptions.typ, such as"at+jwt", together withremoteVerifynow accept tokens that introspection reports as active. Previously every token was rejected, because thetypcheck ran against the introspection response, which has no JWT header. The local JWT check still enforcestyp. That check runs only whenjwksUrlis set andremoteVerify.forceis nottrue. Otherwisetypis not enforced, and the introspection result alone decides. This also fixes MCP servers that setjwtVerifyOptions.typwithremoteVerify.v1.7.17Compare Source
better-auth/better-auth (@better-auth/expo)
v1.7.25Compare Source
v1.7.24Compare Source
Patch Changes
0597f4cThanks @gustavovalverde! -@better-auth/exponow uses thebetter-callcopy thatbetter-authinstalls instead of installing its own, so an Expo app no longer gets a secondbetter-callcopy.v1.7.23Compare Source
v1.7.22Compare Source
v1.7.21Compare Source
Patch Changes
9b40ac6Thanks @bytaesu! - Plugin packages no longer import from thebetter-authroot, so bundlers that split code stop emitting unused Kysely chunks when used withbetter-auth/minimal.v1.7.20Compare Source
v1.7.19Compare Source
Patch Changes
339414fThanks @bytaesu! - The Expo authorization proxy no longer logs a provider configuration error on every OAuth sign-in when a social provider is set up for ID token sign-in only, such as Apple without a client secret.v1.7.18Compare Source
v1.7.17Compare Source
Patch Changes
b00bff0Thanks @bytaesu! - When OAuth state is stored in a cookie, Expo social sign-in now rejects authorization URLs without astateparameter, the same as with the default database storage.better-auth/better-auth (@better-auth/passkey)
v1.7.25Compare Source
v1.7.24Compare Source
Patch Changes
#12502
0597f4cThanks @gustavovalverde! - Official packages now accept anybetter-call1.4 patch release from 1.4.5 as a peer.#12503
87ede79Thanks @gustavovalverde! - Fixed errors from hooks and endpoints turning into generic 500 responses or skipping their error handling in the OAuth provider, Client ID Metadata Document, passkey, SSO, SCIM, and Stripe plugins when the app installs more than one copy ofbetter-call.v1.7.23Compare Source
v1.7.22Compare Source
v1.7.21Compare Source
Patch Changes
#12388
070d101Thanks @gustavovalverde! - If a wildcard inbaseURL.allowedHostscovers your passkeyrpID, such asrpID: "example.com"withallowedHosts: ["*.example.com"], your server now starts without a passkeyorigin. Since 1.7.16 it threw at startup unlessoriginwas set, and passkeys then worked only on the origins listed there, so tenants added at runtime needed a redeploy.In that setup, without
origin, a passkey is accepted only from an exactallowedHostsentry, thefallbackorigin, or an origin listed exactly intrustedOrigins. The host the request names and wildcard entries do not count. To allow tenants added at runtime, return their origins from atrustedOriginsfunction that checks your tenant records. If you setorigin, or no wildcard covers yourrpID, nothing changes.v1.7.20Compare Source
v1.7.19Compare Source
v1.7.18Compare Source
v1.7.17Compare Source
Patch Changes
3ab3dbfThanks @bytaesu! - Passkey registration and sign-in now work when onepasskey()plugin is shared between auth instances where some setbaseURLand others do not. Previously one of the instances could fail withORIGIN_NOT_CONFIGUREDor verify against the other instance's origin settings.better-auth/better-auth (better-auth)
v1.7.25Compare Source
Patch Changes
#12603
ad07eddThanks @gustavovalverde! - An error thrown from an endpoint no longer drops theAccess-Control-Expose-Headersnames that a hook or the endpoint set earlier. The names from both are kept. Before, the error's value replaced the list, so a browser client on another origin could lose access to headers a hook had exposed.Updated dependencies [
69e14d8,2a8750b,75c0821]:v1.7.24Compare Source
Patch Changes
#12593
b77e783Thanks @gustavovalverde! - Looking up a verification value now deletes expired verification rows at most once a minute per server instance, instead of on every lookup. This removes a delete query from most verification reads. Each flow still checks a value's expiry before it accepts the value.Updated dependencies [
0597f4c]:v1.7.23Compare Source
Patch Changes
#12543
d6e9bbdThanks @gustavovalverde! -getTestInstancefrombetter-auth/testnow gives each test file its own MongoDB database and closes its MongoDB client on cleanup. Before, every MongoDB test instance shared thebetter-authdatabase and dropped it during cleanup, so test files running in parallel deleted each other's data.Updated dependencies [
9dc64fb,cfa73e9,41a2526,c10b35d]:v1.7.22Compare Source
Patch Changes
#12324
80c407bThanks @bytaesu! - FixedReferenceError: window is not definedwhen a client session subscription is cleaned up after a test environment such as happy-dom tears down its globals.#12462
d32a30aThanks @bytaesu! - Fixed session polling never firing when the runtime'snavigatordoes not report connectivity.#12324
80c407bThanks @bytaesu! - Fixed client session refresh listeners piling up on the server during SSR.#12321
946177eThanks @bytaesu! - Revoking your current session withrevokeSessionorrevokeSessions, and deleting your account withdeleteUser({ token }), now expire the session cookies, so a cached session is no longer returned afterwards.#12459
d210421Thanks @bytaesu! -getSessionno longer leaves an expired session in the request context after returningnull.#12331
485567eThanks @bytaesu! - OAuth sign-up rejected by auser.create.beforehook returningfalseno longer logs aTypeError. It still fails withunable_to_create_user.#12334
ec3047dThanks @bytaesu! - FixeddeleteOrganizationclearing the session's active organization when abeforeDeleteOrganizationhook rejected the delete. The active organization is now cleared only after the organization is actually deleted.#12330
d521343Thanks @bytaesu! - FixdeferSessionRefreshrefresh requests failing with 415 in Next.js and Nuxt, where the bodylessPOST /get-sessionreached the handler as an empty stream without aContent-Type.#12451
71052afThanks @bytaesu! - On Cloudflare Workers, consuming a verification value no longer hangs when an earlier request for the same identifier ended mid-query. A superseded code can also no longer be consumed while a newer one is being verified on a database without transactions.#12448
79219b4Thanks @bytaesu! - Schema validation now runs when the auth instance is first used instead of when it is created, so a module-scope instance on Cloudflare Workers no longer logs a validation error on every cold start. On every runtime, a mismatch is no longer logged at startup and is reported by the requests that fail.Updated dependencies [
6536174,262adc0,e9d8e59,79219b4]:v1.7.21Compare Source
Patch Changes
#12126
4739122Thanks @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, andprivate_key_jwtclient authentication are fixed the same way, and Sign-In with Ethereum now keeps the email the user supplied instead of a placeholder. Setups with plainStringid columns and other databases are unaffected.#12392
a277020Thanks @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
1c3410aThanks @lakshya-dhariwal! - If you setadvanced.backgroundTasks.handlerand your database adapter runs transactions (the built-in Kysely connection, MongoDB withclient, or Prisma or Drizzle withtransaction: true), email sign-up now keeps the database writes made while sending the verification email or runningonExistingUserSignUp. Before, those writes failed because the sign-up had already been saved. WithemailOTP({ 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. IfsendVerificationEmailthrows, the sign-up succeeds and the error is logged; before, the sign-up failed. To reject a sign-up, use adatabaseHooks.user.create.beforehook. IfonExistingUserSignUpthrows, the error is logged and the request still returns the generic response.#12179
9105261Thanks @ghazy2001! - Generic OAuth providers configured withdiscoveryHeadersnow send those headers when fetching the provider's signing keys from ajwks_urion the same origin asdiscoveryUrl. 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. Ajwks_urion another origin still gets no headers.With
discoveryHeadersset, the discovery request now follows redirects only within the origin ofdiscoveryUrl, so the headers no longer reach another host. If yourdiscoveryUrlredirects to another origin, discovery now fails and Better Auth logs an error. SetdiscoveryUrlto the final URL. Providers withoutdiscoveryHeadersare unaffected.#12401
c3a94c5Thanks @gustavovalverde! - Generic OAuth providers configured withauthorizationHeadersnow 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 withoutauthorizationHeadersare unaffected.refreshAccessTokenandrefreshAccessTokenRequestfrom@better-auth/core/oauth2accept an optionalheadersinput 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
Authorizationwithauthentication: "basic", no longer produce a combined, invalid header on the code exchange or refresh. Client authentication replaces them, including headers a customtokenEndpointAuthhook sets in any casing.#12404
9b40ac6Thanks @bytaesu! - Plugin packages no longer import from thebetter-authroot, so bundlers that split code stop emitting unused Kysely chunks when used withbetter-auth/minimal.#12395
b0ced9dThanks @gustavovalverde! - On Cloudflare Workers, sign-ins with agenericOAuthprovider that usesdiscoveryUrl, 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
5c12074Thanks @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 andnpx auth@latest migrateno longer fail intermittently withschema "…" does not existorrelation "…" does not exist. The startup schema check now reads only the schemas on the connection'ssearch_path, plus any schema set withschemaNameor a schema plugin, andmigratereads 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
e64f624Thanks @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]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.