Skip to content

fix(deps): update better-auth to v1.7.23 - #282

Open
renovate[bot] wants to merge 2 commits into
devfrom
renovate/better-auth
Open

renovate[bot] wants to merge 2 commits into
devfrom
renovate/better-auth

Conversation

@renovate

@renovate renovate Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@better-auth/core (source) 1.7.1 → 1.7.23 age confidence
@better-auth/passkey (source) 1.7.1 → 1.7.23 age confidence
better-auth (source) 1.7.1 → 1.7.23 age confidence

Release Notes

better-auth/better-auth (@​better-auth/core)

v1.7.23

Compare Source

Patch Changes
  • #​12501 cfa73e9 Thanks @​gustavovalverde! - requireMcpAuth now reads the signing keys from the auth instance instead of requesting its own /jwks endpoint, 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 jwksUrl to keep fetching the keys over HTTP.

  • #​12480 c10b35d Thanks @​gustavovalverde! - The advanced.database.validateSchema JSDoc 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.22

Compare Source

Patch Changes
  • #​12333 6536174 Thanks @​bytaesu! - Fix getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema, including with database joins enabled on Drizzle and Prisma. Join resolution now matches references.model against schema keys only.

  • #​12432 262adc0 Thanks @​gustavovalverde! - Reject introspected access tokens that fail claim validation with a 401 UNAUTHORIZED error. When remoteVerify introspection reported an active token whose aud, iss, exp, or nbf claim did not pass the configured checks, verifyBearerToken and verifyAccessTokenRequest threw a plain Error, so resource servers answered with a 500 instead of a WWW-Authenticate challenge. Expired tokens now report token expired and other claim failures report invalid access token, matching local JWKS verification.

  • #​12445 e9d8e59 Thanks @​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.

    createResourceServerChallenge used to throw when an error_description contained a character that RFC 6750 does not allow in that parameter. Better Auth's own DPoP message DPoP 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 in challengeScopes still throw.

    When the request presented a token that failed verification, the 401 Bearer challenge now carries error="invalid_token" and an error_description, following RFC 6750 §3 and §3.1. A request without a token still gets no error code. verifyBearerToken and verifyAccessTokenRequest now set error: "invalid_token" and error_description on their expired, invalid, inactive, and unreadable token errors, and the challenge's response body includes both fields alongside message.

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.

  • #​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.

  • #​11716 1a79da5 Thanks @​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 2d10ae7 Thanks @​gustavovalverde! - With advanced.database.generateId: "serial", filtering an id or reference field with null now compares it with null. Before, the null became 0, so eq null matched no row and, on the memory adapter, ne null also matched rows where the field was unset.

  • #​12425 ef4d4f7 Thanks @​bytaesu! - Telemetry now reports Cloudflare Workers as workerd instead of node when nodejs_compat is enabled. @better-auth/core/env exports the runtime detection it uses.

v1.7.20

Compare Source

Patch Changes
  • #​11904 a3f50d0 Thanks @​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 accept http redirect URIs through the new allowInsecureRedirectUri option. Return true from it for origins you control. The same option lets web clients use localhost callbacks during development. Without the option, redirect URI validation is unchanged.

    If your issuer (baseURL, or jwt.issuer when set) uses http on a non-loopback host, discovery and the iss authorization response parameter now report it as configured instead of rewriting it to https. 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, set baseURL to the public https URL.

    When an authorization request uses a registered http redirect 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.19

Compare Source

Patch Changes
  • #​12317 8412a5f Thanks @​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) with console.error.

  • #​12369 34ee100 Thanks @​bytaesu! - getAccessToken and refreshToken now fail when a provider refuses a token refresh with a 200 status, as GitHub does, instead of returning the expired access token.

v1.7.18

Compare Source

Patch Changes
  • #​12249 9342a73 Thanks @​gustavovalverde! - Resource servers that set verifyOptions.typ, such as "at+jwt", together with remoteVerify now accept tokens that introspection reports as active. Previously every token was rejected, because the typ check ran against the introspection response, which has no JWT header. The local JWT check still enforces typ. That check runs only when jwksUrl is set and remoteVerify.force is not true. Otherwise typ is not enforced, and the introspection result alone decides. This also fixes MCP servers that set jwtVerifyOptions.typ with remoteVerify.

v1.7.17

Compare Source

v1.7.16

Compare Source

Patch Changes
  • #​12198 f25081a Thanks @​bytaesu! - Generic OAuth providers whose discovery document has a jwks_uri now reject a user profile whose sub differs from the ID token's sub. Direct ID-token sign-in and linking with a generic OAuth provider now resolve the profile from the verified ID token only and ignore a submitted access or refresh token.

  • #​12198 f25081a Thanks @​bytaesu! - Account linking and new OAuth users now count an email as verified only when the provider claim is true or the string "true", which covers generic OAuth, Cognito, and Microsoft Entra ID claims sent as strings. Any other emailVerified value, including a non-boolean value returned from mapProfileToUser such as 1, now reads as unverified.

  • #​12198 f25081a Thanks @​bytaesu! - The Zoom social provider now applies its configured provider options, so disableSignUp, requireEmailVerification, and overrideUserInfoOnSignIn take effect for Zoom sign-ins.

v1.7.15

Compare Source

Patch Changes
  • #​12106 9ef0c5b Thanks @​bytaesu! - Built-in social providers no longer follow HTTP redirects on token exchange, refresh, verification, and signing key (JWKS) requests, matching the other server-side OAuth requests.

v1.7.14

Compare Source

Patch Changes
  • #​12045 2947ab7 Thanks @​honuuk! - Kakao sign-in now passes loginHint to Kakao, so the Kakao Account login page opens with the ID field prefilled.

v1.7.13

Compare Source

Patch Changes
  • #​11997 2712441 Thanks @​bytaesu! - The Cloudflare provider now accepts tokenEndpointAuth: { method }. The existing tokenEndpointAuthMethod option is marked as deprecated and remains supported for backward compatibility.

  • #​11948 1cf4b2c Thanks @​allenzhou101! - Allow the Vercel social provider to configure token endpoint authentication, including dynamic OIDC tokens and private key JWT client assertions, without replacing the built-in sign-in flow.

v1.7.12

Compare Source

Patch Changes
  • #​11924 681aa5c Thanks @​bytaesu! - APIError.from() accepts { cause } as a third argument to keep the underlying error for server-side callers without exposing it in the response.

  • #​11931 4bc78ba Thanks @​bytaesu! - ID token sign-in now rejects tokens when the provider has no client ID, because their audience cannot be checked and a token issued to another app would otherwise be accepted. Set clientId on the provider to every client ID your apps sign in with.

  • #​11919 876608d Thanks @​bytaesu! - A custom Facebook getUserInfo no longer receives client-submitted access tokens issued to another Facebook app, and ID tokens missing exp or iat are now rejected.

  • #​11918 083a743 Thanks @​alpcanaydin! - Fix mapProfileToUser failing to typecheck under exactOptionalPropertyTypes when it returns undefined for name, email or image, for example to drop the provider's profile picture.

  • #​11920 492134a Thanks @​bytaesu! - Restore the Twitch and Paybin ID token handling from before 1.7.11, which made account info fail once the ID token stored at sign-in expired.

v1.7.11

Compare Source

Patch Changes
  • #​11623 ce96569 Thanks @​cpojer! - Reduce installation size by removing the semantic conventions production dependency while preserving all instrumentation attribute keys.

  • #​11907 2f6ca3f Thanks @​bytaesu! - Fix plugins whose init returns options: undefined, such as testUtils(), failing to typecheck when exactOptionalPropertyTypes is enabled.

  • #​11884 dfd8dd2 Thanks @​bytaesu! - Twitch and Paybin sign-in now verify ID token signatures and identity claims before mapping profiles, with 30 seconds of clock tolerance. Custom Paybin issuers must expose RS256 signing keys at <issuer>/.well-known/jwks.json.

v1.7.10

Compare Source

Patch Changes
  • #​11612 fedd055 Thanks @​vhinayindia! - If your resource server verifies access tokens with verifyAccessTokenRequest or verifyBearerToken and a jwksUrl, including through the MCP plugin, a key set that cannot be reached at all, for example a refused connection, now throws an error. Before, the token was rejected as invalid with 401 "no token payload", which hid the outage. A key set that answers with an HTTP error already threw.

    With remoteVerify configured, such a failure no longer falls back to remote introspection.

    The OAuth provider's /oauth2/introspect, /oauth2/userinfo and /oauth2/revoke behave the same way with the JWT plugin's jwks.remoteUrl: they return 500 instead of reporting the token as invalid.

  • #​11805 bbd0a19 Thanks @​gustavovalverde! - Servers that verify JWTs against a key set now refetch that key set at most once every 30 seconds per server process when a token names a key ID (kid) the cached set does not contain. This covers the OAuth provider plugin's introspection, revocation, UserInfo, and logout endpoints, and resource servers that call verifyAccessTokenRequest or verifyBearerToken with jwksUrl. Previously every such token caused a new fetch: a remote request with jwksUrl or jwks.remoteUrl, or otherwise a read of the jwks table. Anyone could send tokens with made-up kid values to force one fetch per request, and the UserInfo endpoint needs no client credentials.

    Concurrent verifications now share one fetch, and a key set fetch that takes longer than 5 seconds fails with a JWKSTimeout error instead of waiting indefinitely.

    A token signed with a newly published key still verifies without waiting for the 5-minute cache to expire. It can be rejected for up to 30 seconds if the key set was already refetched for another unknown kid in that time. No configuration change is needed.

v1.7.9

Compare Source

v1.7.8

Compare Source

Patch Changes
  • #​11512 4175b34 Thanks @​bytaesu! - Align the installed @better-auth/utils version with better-call while accepting ^0.4.2 || ^0.5.0 across official package peers.

  • #​11592 435645e Thanks @​drewsephski! - Fix Atlassian user info errors being logged as coming from Figma.

  • #​11625 369176e Thanks @​gustavovalverde! - Fixed single-use checks for apps that set advanced.database.generateId: "uuid". Default id generation is unaffected, and no migration is needed.

    • On SQLite and MySQL, SAML sign-in, DPoP-bound requests checked against the database replay store, private_key_jwt client authentication, and magic link or email OTP sign-ins that adopt an unverified account failed with a NOT NULL error on the id column. They now work. SIWE sign-in ignored the email field and used the wallet-derived address; it now uses the supplied email when no other account has it.
    • On Postgres and MongoDB, a reused SAML assertion, DPoP proof, or client assertion was accepted. Each one is now accepted only once.

    With generateId: "serial", behavior is unchanged: these checks need string ids, and Better Auth now logs a warning the first time one of these flows runs.

  • #​11749 e78f15a Thanks @​gustavovalverde! - ID token verification now allows 30 seconds of clock difference between your server and the identity provider when checking exp, nbf, and iat. Previously, a provider whose clock ran even slightly ahead (for example, an nbf set a fraction of a second in the future) made sign-in fail. This affected generic OAuth providers configured with discoveryUrl since 1.7.0, ID token sign-in with the built-in social providers, and Google One Tap. Tokens up to 30 seconds past exp are now also accepted. No configuration change is needed. A custom verifyIdToken replaces this check and must set its own tolerance, and the SSO plugin's OIDC sign-in is unchanged.

  • #​11663 60525e0 Thanks @​kaiizer777! - Fixed Microsoft Entra ID sign-in with an ID token (signIn.social with idToken, and linking an account with an ID token) rejecting every token. Microsoft publishes its signing keys without an alg field, which made verification fail. Those keys are now treated as RS256, and Microsoft ID tokens signed with any other algorithm are rejected. The redirect sign-in flow was not affected.

  • #​11515 916ef5c Thanks @​BilalAtique! - If you pass client to mongodbAdapter on a replica set, concurrent requests that write the same documents no longer fail with a 500. Before, MongoDB aborted all but one of them with a write conflict, so a SCIM directory that provisions several users at once returned 500 for most of them. The adapter now retries such a transaction, as MongoDB requires, for up to 120 seconds or until your MongoClient's timeoutMS. Under contention a request can take longer instead of failing.

    A retry runs the work again. databaseHooks before hooks can run more than once for one request, and after hooks still run once, after the commit. Work that the request does outside the database before it commits can also repeat on a retried request. For example, an email sign-up can send its verification email twice. Requests that succeed on the first attempt are unaffected, and so are other adapters.

  • #​11718 1d95ebf Thanks @​bytaesu! - Fix missing device sessions and failed automatic session switching after cache eviction when storeSessionInDatabase is enabled and preserveSessionInDatabase is disabled. Automatic switching now follows the order of held sessions, and large lists or sessions whose users no longer exist no longer cause valid sessions to disappear.

  • #​10956 6214610 Thanks @​disbell! - Native OAuth clients and Client ID Metadata Documents can now use custom-scheme redirect URIs with a host and a path, such as Cursor's cursor://anysphere.cursor-mcp/oauth/callback. Previously, only the authority-free reverse-domain form, such as com.example.app:/callback, was accepted, and these registrations failed with invalid_redirect_uri.

    Cursor also omits application_type when it registers, so the web default still rejects it. To accept Cursor, set the new clientRegistrationDefaultApplicationType option to "infer". A dynamic registration that omits application_type then becomes native when any of its redirect URIs uses a custom scheme, and every redirect URI must pass the native rules. Setting "native" treats every registration that omits the field as native. The default remains "web", and an application_type the client sends is never overridden.

    Pairwise clients (subject_type: "pairwise") cannot use these host-bearing custom-scheme redirect URIs. Web clients are unaffected: they still accept only https redirect URIs on non-loopback hosts.

  • #​11626 67743ed Thanks @​gustavovalverde! - Password resets and password changes no longer keep the new password when revoking the user's sessions fails. With revokeSessionsOnPasswordReset or revokeOtherSessions, database sessions are revoked and the password is saved in one transaction when transactions are enabled for the adapter, so a failure leaves the old password and sessions in place. Sessions in secondary storage are still removed after commit, on a best-effort basis. This covers /reset-password, the email OTP and phone number reset endpoints, and /change-password. onPasswordReset now runs after sessions are revoked, so a throwing callback no longer leaves them active, and a callback that lists the user's sessions no longer sees the revoked ones.

  • #​11712 c46d2a6 Thanks @​bytaesu! - Fix misleading errors for invalid runtime-provided AsyncLocalStorage values in the edge and browser fallback, and recognize AsyncLocalStorage initialized after importing Better Auth but before first use.

  • #​11643 92dfcea Thanks @​gustavovalverde! - A sign-up that fails after its session is created no longer leaves that session in secondary storage. With storeSessionInDatabase enabled and preserveSessionInDatabase off, the secondary-storage copy is written only after the sign-up commits, and listing a user's sessions now reads the database, so a session whose cached copy failed to write is still listed and revoked. With other secondary-storage settings, sign-up, passkey registration and SSO sign-in with resolveUser keep the session write inside their transaction, so a storage failure rolls back the new user, passkey or account instead of keeping them without a session. A session revoked by a session.create.after database hook also stays revoked.

  • #​11645 a9f455d Thanks @​gustavovalverde! - On database adapters without transactions enabled, a request that fails after writing data now still runs the after hooks for those writes, such as databaseHooks after callbacks and secondary-storage session cleanup. Previously they were skipped even though the writes were kept.

  • #​11711 9725f1b Thanks @​bytaesu! - Fix subsequent authentication requests hanging after async context initialization is interrupted.

v1.7.7

Compare Source

v1.7.6

Compare Source

Patch Changes

v1.7.5

Compare Source

Patch Changes
  • #​11203 cb627eb Thanks @​dshukertjr! - Add a database.schemaName option for direct PostgreSQL connections. When set, the adapter and the CLI qualify every statement with that schema, so auth generate writes a schema-qualified migration that creates the schema before its tables instead of relying on the connection's search_path.

  • #​11290 dae97ed Thanks @​bytaesu! - Restore database option type inference for projects that do not use Cloudflare Workers.

v1.7.4

Compare Source

Patch Changes
  • #​11210 3ff842a Thanks @​bytaesu! - Prevent bundlers such as Metro from failing when the optional OpenTelemetry API is not installed.

  • #​11224 c1756a2 Thanks @​bytaesu! - Add experimental.instrumentation.enabled to disable Better Auth OpenTelemetry span creation per auth instance. Instrumentation remains enabled by default and independent of usage reporting.

v1.7.3

Compare Source

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.

  • #​9908 76d311f Thanks @​harshil1712! - Add Cloudflare as a built-in social provider, with support for client-secret authentication and PKCE clients without a secret.

  • #​11101 3e9e197 Thanks @​bytaesu! - Add a custom token endpoint authentication strategy for providers that require non-standard request parameters.

  • #​11068 157ec8d Thanks @​bytaesu! - Improve request IP validation performance.

  • #​11102 baa08f4 Thanks @​bytaesu! - Fix TikTok sign-in and token refresh failing when configured with the documented clientKey and clientSecret options.

  • #​11129 9e36635 Thanks @​bytaesu! - Improve PayPal authorization code and refresh token requests, including PKCE parameter handling.

  • #​11178 be0e007 Thanks @​bytaesu! - Report missing tables, missing columns, and required columns Better Auth never writes during initialization, with guidance for fixing them. Kysely checks the live database schema. Authentication requests await the same check and are rejected if the schema does not match.

    Validation is enabled by default, including in production. Set advanced.database.validateSchema: false to disable runtime validation. auth migrate refuses to apply changes when required unwritten columns need manual repair.

  • #​11134 a2bae0c Thanks @​bytaesu! - Improve Reddit token requests with OAuth-compliant Basic authentication and redirect protection.

  • #​11189 1a1b7d5 Thanks @​bytaesu! - Make consumeOne and incrementOne optional again for custom database adapters, using guarded fallbacks when native methods are absent. Fallbacks require atomic conditional writes and accurate affected-row counts. Fallback increments can fail when contention exhausts their retries.

  • #​11153 2220ee7 Thanks @​bytaesu! - Restore sign-in compatibility with 1.6 databases by identifying accounts with (providerId, accountId) and removing the issuer requirement introduced in 1.7.0. Upgrading from 1.6 no longer requires an account schema migration. Ambiguous account keys are rejected instead of selecting an arbitrary account.

    If you applied the 1.7.0 through 1.7.2 account schema, remove its issuer unique index before upgrading. For SQL databases, also make issuer nullable or remove the column so sign-ups and account linking can succeed. auth migrate does not perform this cleanup. Follow the upgrade guide for database-specific steps.

v1.7.2

Compare Source

Patch Changes
  • #​12572 69e14d8 Thanks @​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 %20 became +, 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 2a8750b Thanks @​gustavovalverde! - The default in-memory DPoP replay store used by verifyAccessTokenRequest no 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 75c0821 Thanks @​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, or requireMcpAuth failed with a 500 error unless verification.storeInDatabase: true was set. Used proofs are now recorded in secondary storage, so a replayed proof is still rejected across instances. createDpopReplayStore now also accepts the auth context, as createDpopReplayStore(await auth.$context), and picks the same storage.

better-auth/better-auth (@​better-auth/passkey)

v1.7.23

Compare Source

v1.7.22

Compare Source

v1.7.21

Compare Source

Patch Changes
  • #​12388 070d101 Thanks @​gustavovalverde! - If a wildcard in baseURL.allowedHosts covers your passkey rpID, such as rpID: "example.com" with allowedHosts: ["*.example.com"], your server now starts without a passkey origin. Since 1.7.16 it threw at startup unless origin was 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 exact allowedHosts entry, the fallback origin, or an origin listed exactly in trustedOrigins. The host the request names and wildcard entries do not count. To allow tenants added at runtime, return their origins from a trustedOrigins function that checks your tenant records. If you set origin, or no wildcard covers your rpID, nothing changes.

v1.7.20

Compare Source

v1.7.19

Compare Source

v1.7.18

Compare Source

v1.7.17

Compare Source

Patch Changes
  • #​12225 3ab3dbf Thanks @​bytaesu! - Passkey registration and sign-in now work when one passkey() plugin is shared between auth instances where some set baseURL and others do not. Previously one of the instances could fail with ORIGIN_NOT_CONFIGURED or verify against the other instance's origin settings.

v1.7.16

Compare Source

Patch Changes
  • #​12198 f25081a Thanks @​bytaesu! - Passkey registration, device authorization, two-factor enrollment and verification, social account linking, and phone number changes now reject a session re

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/Paris)

  • Branch creation
    • "before 6am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • 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 enabled auto-merge (squash) November 15, 2026 23:03
@renovate
renovate Bot force-pushed the renovate/better-auth branch 2 times, most recently from b9f6d91 to c1af0b8 Compare November 16, 2026 15:51
@renovate renovate Bot changed the title fix(deps): update better-auth to v1.7.22 fix(deps): update better-auth to v1.7.23 Nov 16, 2026
@renovate
renovate Bot force-pushed the renovate/better-auth branch from de918a7 to 721984e Compare November 16, 2026 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants