rebase! chore(deps): update dev dependencies#346
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
better-auth | 67e0799 | May 12 2026, 07:35 AM |
commit: |
8a57355 to
b837eb5
Compare
b837eb5 to
6750127
Compare
69526bd to
8a61595
Compare
8a61595 to
0e32cac
Compare
Collaborator
|
@renovate rebase |
0e32cac to
a6c3ec5
Compare
a6c3ec5 to
42565a4
Compare
Contributor
Author
|
Collaborator
|
@renovate rebase |
Collaborator
|
@renovatebot rebase |
42565a4 to
2805be1
Compare
2805be1 to
8c82bec
Compare
8c82bec to
11668e4
Compare
11668e4 to
32aee5a
Compare
32aee5a to
67e0799
Compare
Contributor
|
Deployment failed with the following error: Learn More: https://vercel.com/maximogarciamartinezs-projects?upgradeToPro=build-rate-limit |
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.
This PR contains the following updates:
4.3.1→4.4.54.0.0→4.0.314.2.1→14.3.01.5.5→1.6.101.3.2→1.3.512.6.2→12.9.011.0.1→11.1.05.8.1→5.11.010.0.3→10.3.02.13.1→2.13.44.3.1→4.4.51.1.1→1.1.24.0.18→4.1.63.5.29→3.5.343.2.7→3.2.84.72.0→4.90.02.8.3→2.9.0Release Notes
nuxt/nuxt (@nuxt/schema)
v4.4.5Compare Source
👉 Changelog
compare changes
🔥 Performance
isIgnoredrelative (#35015)🩹 Fixes
clientServerwithssr: false(#34959)/+ overridessr: true(#34990)optimizeDeps.includein pre-bundle hint (#34976).envbefore resolving nuxt schema (#34958)serverHandlersarray afternitro:config(#34985)getCachedDatafor concurrent callers sharing a key (#34999)useFetch(#35003)📖 Documentation
🏡 Chore
jiti(c8102228f)@vue/compiler-sfc(cd404a14c)✅ Tests
buildDirper matrix project for shared fixtures (#35007)❤️ Contributors
v4.4.4Compare Source
v4.4.2Compare Source
nuxt/test-utils (@nuxt/test-utils)
v4.0.3Compare Source
👉 Changelog
compare changes
🩹 Fixes
compilerOptionsconditionally (#1659)isActiveslot props (#1640)startServer(#1675)🏡 Chore
❤️ Contributors
v4.0.2Compare Source
👉 Changelog
compare changes
🩹 Fixes
🤖 CI
❤️ Contributors
v4.0.1Compare Source
👉 Changelog
compare changes
🩹 Fixes
mockNuxtImporttypes when using string target (#1592)defineConfigfromvite(1aa5e8748)ResourceLoaderremoval in jsdom v28 (#1611)vitest/environmentsimport warning (#1627)🏡 Chore
vitest-environment-nuxtversions (f5ec72127)pkg-pr-newprereleasevitest-environment-nuxt(#1601)✅ Tests
🤖 CI
pkg-pr-newprerelease (#1598)❤️ Contributors
vueuse/vueuse (@vueuse/nuxt)
v14.3.0Compare Source
🚀 Features
controlsoption - by @kricsleo in #5191 (0cb03)maxHeightto limit autosize growth - by @palamarchukser, @antfu and @9romise in #5324 (1a3e5)🐞 Bug Fixes
./package.jsonexport to all packages - by @babu-ch and @OrbisK in #5343 (0d989)ignoreDeprecationsfor twoslash TS 6.0 compat - by @antfu and Claude Opus 4.6 (1M context) in #5367 (9d1eb)resolveRef- by @ntnyq in #5307 (49da8)start()for string selectors - by @Mini-ghost in #5374 (3341f)🏎 Performance
deepRefwithshallowRefwhere appropriate - by @9romise in #5293 (80004)View changes on GitHub
better-auth/better-auth (better-auth)
v1.6.10Compare Source
Patch Changes
#8339
1e0f26dThanks @ping-maxwell! - fix(captcha): breaks email-otp flow#9484
8c1e917Thanks @ping-maxwell! - fix: warn for cookie-plugin being last in array#9437
b2d655cThanks @cyphercodes! - Allow organization invitation role input types to accept dynamic access control roles.#9497
09f1327Thanks @bytaesu! - Endpoints that set cookies before redirecting (such as social sign-incallbacks and magic-link verification) no longer emit each
Set-Cookieentry twice on the response.
#9387
906b7b3Thanks @bytaesu! - The bearer plugin now produces a single entry per cookie name when mergingits session token into the request
Cookieheader. Previously the mergedheader could carry two entries for the same name if the request already
had a stale session cookie, which would surface to downstream code that
picks the first occurrence.
#9475
e9c978eThanks @jaydeep-pipaliya! - fix(username): respect callbackURL on/sign-in/usernameThe endpoint accepted a
callbackURLbody field but ignored it, soauthClient.signIn.username({ ..., callbackURL })silently did nothingwhile
authClient.signIn.emailredirected as expected. The handler nowsets a
Locationheader whencallbackURLis provided and returns{ redirect, url }alongsidetoken/user, matching the email flow.#9440
e71aad3Thanks @cyphercodes! - Clear organization active hook state after sign-out souseActiveMemberRoledoes not retain a previous user's role in SPA sign-out/sign-in flows.#9402
80a655dThanks @onmax! - Revalidate the client session after admin impersonation starts or stops.#9503
15ff28aThanks @bytaesu! -internalAdapter.deleteAccountparameter renamed fromaccountIdtoidto reflect that it queries by primary key, not theaccountIdcolumn. No runtime behavior change.#9268
88a7c67Thanks @ping-maxwell! - fix: openAPI schema for POST /sign-in/social mis-declares required fields#8839
9a7b51dThanks @dipan-ck! - Apply email enumeration protection whenemailAndPassword.autoSignInis false. Duplicate sign-ups now return a synthetic user (token: null) and triggeronExistingUserSignUp, and new sign-ups skip auto sign-in (token: null)—even withoutrequireEmailVerification, aligning with the docs.#9065
1b25902Thanks @ping-maxwell! - non-ASCII error_description in generic-oauth callback routes causes TypeError on redirect#9349
cf59136Thanks @ping-maxwell! - fix(organization): re-export field types to prevent TS2742 with additionalFields#9453
a597ee0Thanks @mausic! - The organization plugin'scancelPendingInvitationsOnReInviteoption now actually cancels the prior pending invitation when re-inviting the same email. Previously the option had no effect — re-inviting always failed withUSER_IS_ALREADY_INVITED_TO_THIS_ORGANIZATION#9456
fc02cedThanks @cyphercodes! - Reject OAuth callbacks when provider user info omits the account id to avoid linking accounts under the literalundefinedid.#9461
9f1ef1fThanks @cyphercodes! - ExposeauthClient.siwe.getNonce()as a compatibility alias for the SIWE nonce endpoint.#9369
36ef808Thanks @ping-maxwell! - fix: incorrect email casing across one-tap, email-otp & email-verification#9239
c1336c5Thanks @GautamBytes! - Fixorganization.setActiveTeamso it only accepts teams from the current active organization.#7764
3a9a2c3Thanks @programming-with-ia! - chore: expose refreshUserSessions on internal adapter#9521
fde0432Thanks @ping-maxwell! - fix: improve link accessibility issuesUpdated dependencies [
2220a6d]:v1.6.9Compare Source
Patch Changes
815ecf6]:v1.6.8Compare Source
Patch Changes
#9253
856ab24Thanks @baptisteArno! - fix(organization): allow passing id throughbeforeCreateTeamandbeforeCreateInvitationMirrors #4765 for teams and invitations:
adapter.createTeamandadapter.createInvitationnow passforceAllowId: true, so ids returned from the respective hooks survive the DB insert.#9331
9aa8e63Thanks @gustavovalverde! - fix(oauth): supportmapProfileToUserfallback for providers that may omit emailSocial sign-in with OAuth providers that may return no email address (Discord phone-only accounts, Apple subsequent sign-ins, GitHub private emails, Facebook, LinkedIn, and Microsoft Entra ID managed users) can now be unblocked by synthesizing an email inside
mapProfileToUser. Rejection logger messages now point at this workaround and at the new "Handling Providers Without Email" docs section.Provider profile types now reflect where
emailcan benullor absent:DiscordProfile.emailisstring | nulland optional (absent when theemailscope is not granted)AppleProfile.emailis optionalGithubProfile.emailisstring | nullFacebookProfile.emailis optionalFacebookProfile.email_verifiedis optional (Meta's Graph API does not include this field)LinkedInProfile.emailis optionalLinkedInProfile.email_verifiedis optionalMicrosoftEntraIDProfile.emailis optionalTypeScript consumers who previously dereferenced
profile.emaildirectly insidemapProfileToUserwill see a compile error that matches the runtime reality; use a nullish-coalescing fallback (profile.email ?? ...) or null-check the field.Sign-in still rejects with
error=email_not_found(social callback) orerror=email_is_missing(Generic OAuth plugin) when neither the provider normapProfileToUserproduces an email. First-class support for users without an email, keyed on(providerId, accountId)per OpenID Connect Core §5.7, is tracked in #9124.Updated dependencies [
9aa8e63]:v1.6.7Compare Source
Patch Changes
#9211
307196aThanks @stewartjarod! - PreserveSet-Cookieheaders accumulated onctx.responseHeaderswhen an endpoint throwsAPIError. Cookie side-effects fromdeleteSessionCookie(and anyctx.setCookie/ctx.setHeadercalls before the throw) are no longer silently discarded on the error path.#9292
4f373eeThanks @gustavovalverde! - Accept an array of Client IDs on providers that verify ID tokens by audience (Google, Apple, Microsoft Entra, Facebook, Cognito). The first entry is used for the authorization code flow; all entries are accepted when verifying an ID token'saudclaim, so a single backend can serve Web, iOS, and Android clients with their platform-specific Client IDs.Passing a single string keeps working; no migration needed.
Also exports
getPrimaryClientIdfrom@better-auth/core/oauth2for provider authors: it returns the primary Client ID (the raw string, or the entry at array index 0), paired withclientSecretfor the authorization code flow. Providers now reject empty arrays, empty strings, and missing config at sign-in time instead of silently producing a malformed authorization URL. Google, Apple, and Facebook require bothclientIdandclientSecretbecause each of those providers mandates a client secret for their server-side code exchange. Microsoft Entra and Cognito only requireclientId, since both support public-client flows with PKCE alone (no secret).#9293
e1b1cfcThanks @gustavovalverde! - Guard againstc.bodybeing undefined inparseState. Callback requests that arrive as GET leavec.bodyunset in some runtimes, which causedc.body.stateto throw aTypeErrorbefore the existing error redirect could run. The state lookup now short-circuits on the query parameter and falls back toc.body?.statesafely, so a callback without a state parameter redirects to the error page instead of crashing.#4894
d053a45Thanks @Kinfe123! - FirecallbackOnVerificationwhen a phone number is verified withupdatePhoneNumber: true. The callback previously only ran on initial verification, so consumers relying on it (e.g. to sync verified numbers to an external system) would miss the event when an authenticated user changed their number.Updated dependencies [
307196a,4a180f0,4f373ee]:v1.6.6Compare Source
Patch Changes
#9214
4debfb6Thanks @ping-maxwell! - fix(custom-session): use coerced boolean for disableRefresh query param validation#9235
9ea7eb1Thanks @bytaesu! - Preserve thePartitionedattribute when thecustomSessionplugin and framework integrations forwardSet-Cookieheaders.#9266
ab4c10fThanks @ping-maxwell! - fix(organization): infer team additional fields correctly#9219
a61083eThanks @bytaesu! - Allow removing a phone number withupdateUser({ phoneNumber: null }). The verified flag is reset atomically. Changing to a different number still requires OTP verification throughverify({ updatePhoneNumber: true }).#9226
e64ff72Thanks @gustavovalverde! - Consolidate host/IP classification behind@better-auth/core/utils/hostand close several loopback/SSRF bypasses that the previous per-package regex checks missed.Electron user-image proxy: SSRF bypasses closed (
@better-auth/electron).fetchUserImagepreviously gated outbound requests with a bespoke IPv4/IPv6 regex that missed multiple vectors. All of the following were reachable in production and are now blocked:http://tenant.localhost/and other*.localhostnames (RFC 6761 reserves the entire TLD for loopback).http://[::ffff:169.254.169.254]/(IPv4-mapped IPv6 to AWS IMDS, the classic SSRF bypass).http://metadata.google.internal/,http://metadata.goog/(GCP instance metadata).http://instance-data/,http://instance-data.ec2.internal/(AWS IMDS alternate FQDNs).http://100.100.100.200/(Alibaba Cloud IMDS; lives in RFC 6598 shared address space100.64/10, which the old regex did not cover).http://0.0.0.0:PORT/(the Linux/macOS kernel routes the unspecified address to loopback: Oligo's "0.0.0.0 Day").http://[fc00::...]/,http://[fd00::...]/(IPv6 ULA per RFC 4193) and IPv6 link-localfe80::/10, neither of which the regex recognized.Documentation ranges (RFC 5737 / RFC 3849), benchmarking (
198.18/15), multicast, and broadcast are also now rejected.better-auth:0.0.0.0is no longer treated as loopback. The previousisLoopbackHostimplementation inpackages/better-auth/src/utils/url.tsclassified0.0.0.0alongside127.0.0.1/::1/localhost.0.0.0.0is the unspecified address, not loopback; treating it as such lets browser-origin requests reach localhost-bound dev services (Oligo's "0.0.0.0 Day"). The helper now accepts the full127.0.0.0/8range and any*.localhostname, and rejects0.0.0.0.better-auth: trusted-origin substring hardening.getTrustedOriginspreviously usedhost.includes("localhost") || host.includes("127.0.0.1")when deciding whether to add anhttp://variant for a dynamicbaseURL.allowedHostsentry. Misconfigurations likeevil-localhost.comor127.0.0.1.nip.iowould incorrectly gain an HTTP origin in the trust list. The check now uses the shared classifier, so only real loopback hosts get the HTTP variant.@better-auth/oauth-provider: RFC 8252 compliance.127.0.0.0/8range (not just127.0.0.1) plus[::1], with port-flexible comparison. Port-flexible matching is limited to IP literals; DNS names such aslocalhostcontinue to use exact-string matching per §8.3 ("NOT RECOMMENDED" for loopback).validateIssuerUrluses the shared loopback check rather than a two-hostname literal comparison.New module:
@better-auth/core/utils/host. ExposesclassifyHost,isLoopbackIP,isLoopbackHost, andisPublicRoutableHost. One RFC 6890 / RFC 6761 / RFC 8252 implementation that handles IPv4, IPv6 (including bracketed literals, zone IDs, IPv4-mapped addresses, and 6to4 / NAT64 / Teredo tunnel forms with embedded-IPv4 recursion), and FQDNs, with a curated cloud-metadata FQDN set. All bespoke loopback/private/link-local checks across the monorepo now route through it.Updated dependencies [
b5742f9,a844c7d,e64ff72]:v1.6.5Compare Source
Patch Changes
#9119
938dd80Thanks @GautamBytes! - clarify recommended production usage for the test utils plugin#9087
0538627Thanks @ramonclaudio! - fix(client): refetch session after/change-passwordand/revoke-other-sessionsUpdated dependencies []:
v1.6.4Compare Source
Patch Changes
#9205
9aed910Thanks @gustavovalverde! - fix(two-factor): revert enforcement broadening from #9122Restores the pre-#9122 enforcement scope. 2FA is challenged only on
/sign-in/email,/sign-in/username, and/sign-in/phone-number, matching the behavior that shipped through v1.6.2. Non-credential sign-in flows (magic link, email OTP, OAuth, SSO, passkey, SIWE, one-tap, phone-number OTP, device authorization, email-verification auto-sign-in) are no longer gated by a 2FA challenge by default.A broader enforcement scope with per-method opt-outs and alignment to NIST SP 800-63B-4 authenticator assurance levels is planned for a future minor release.
#9068
acbd6efThanks @GautamBytes! - Fix forced UUID user IDs from create hooks being ignored on PostgreSQL adapters whenadvanced.database.generateIdis set to"uuid".#9165
39d6af2Thanks @gustavovalverde! - chore(adapters): require patcheddrizzle-ormandkyselypeer versionsNarrows the
drizzle-ormpeer to^0.45.2and thekyselypeer to^0.28.14. Both new ranges track the minor line that carries the vulnerability fix and nothing newer, so the adapters only advertise support for versions that have actually been tested against. Consumers on older ORM releases see an install-time warning and can upgrade alongside the adapter; the peer is marked optional, so installs do not hard-fail.Updated dependencies [
39d6af2]:v1.6.3Compare Source
Patch Changes
#9131
5142e9cThanks @gustavovalverde! - harden dynamicbaseURLhandling for directauth.api.*calls and plugin metadata helpersDirect
auth.api.*callsAPIErrorwith a clear message when the baseURL can't be resolved (no source and nofallback), instead of leavingctx.context.baseURL = ""for downstream plugins to crash on.allowedHostsmismatches on the direct-API path toAPIError.advanced.trustedProxyHeaderson the dynamic path (defaulttrue, unchanged). Previouslyx-forwarded-host/-protowere unconditionally trusted withallowedHosts; they now go through the same gate as the static path. The default flip tofalseships in a follow-up PR.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.