Repository navigation
chore(deps): Update all non-major dependencies - #208
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 16, 2026 10:57
4830dda to
a59b660
Compare
chertik77
force-pushed
the
renovate/all-minor-patch
branch
from
November 16, 2026 20:24
d21cdf2 to
7f03d9b
Compare
This branch was successfully 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.18→^1.7.22^5.28.8→^5.30.2^7.0.3→^7.0.6^1.168.48→^1.169.0^4.0.4→^4.0.9^6.2.1→^6.3.0^1.7.18→^1.7.22^1.70.0→^1.72.0^14.10.1→^14.13.0^3.9.10→^3.10.17.91.0→7.92.0^0.9.0→^0.10.0^8.72.1→^8.72.2^8.3.6→^8.3.8Release Notes
better-auth/better-auth (@better-auth/passkey)
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
Rel1cx/eslint-react (@eslint-react/eslint-plugin)
v5.30.2Compare Source
🐞 Fixes
react-web-api/no-leaked-fetch: non-globalfetchcalls are no longer checked: a barefetch(...)whose name is bound by an enclosing scope (ex: a localfunction fetch() {}) and member calls on non-global objects (ex:api.fetch(...)) are ignored, whilewindow.fetch(...),globalThis.fetch(...), andself.fetch(...)are still recognized. (#2116, closes #2072)Full Changelog: Rel1cx/eslint-react@v5.30.1...v5.30.2
v5.30.1Compare Source
🐞 Fixes
react-x/no-duplicate-key: in.map()callbacks, all statically known keys are now treated as repeating, not only bare string literals.react-jsx/no-leaked-semicolon: same-line leaked semicolons after an expression container are now detected (ex:<div>{x};</div>,<div>{cond && <span />};</div>).🏗️ Internal
Full Changelog: Rel1cx/eslint-react@v5.30.0...v5.30.1
v5.30.0Compare Source
✨ New
@eslint-react/eslint-plugin: added theall-type-checkedpreset, which extendsallwith the rules that require type information. (#2095)@eslint-react/eslint-plugin: added the experimental@eslint-react/unstable-exhaustive-depsrule, forked fromexhaustive-deps, with ahooksoption modeled on Biome'suseExhaustiveDependencies(closureIndex/dependenciesIndexfor custom Hooks, andstableResultfor stable results). The rule lives in the unified plugin's ownsrc/ruleswhile incubating and is enabled in theallpreset (and thereby inall-type-checked). (#1698, #2078, #2095) Thanks to @dgesteves!react-x/set-state-in-effect: reworked around explicit effect roots, recursive value resolution, and a synchronous call graph. Stable aliases, multi-level helpers, named setups, IIFEs, anduseCallback/useMemo/useEffectEventwrappers now share one resolution path; indirect diagnostics point at the effect-side trigger and dedupe by setter sink; async functions remain deferred. (#2075)react-x/static-components: JSX member expression tags (ex:<Namespace.Bar />) are now analyzed. (#2114)🐞 Fixes
react-x/error-boundaries: optional-chainedcreateElementcalls are recognized as JSX-like return values. (#2084)react-x/no-direct-mutation-state: state assignments in nested constructor blocks (if, loops,try, and bare blocks) are no longer reported. (#2088)react-x/no-duplicate-key: only keys that provably have a duplicate are now reported. Unique siblings in a partially duplicate group (ex:[A, B, B]) are no longer reported, and duplicates followed by a unique key (ex:[A, A, B]) are now correctly reported; keys collected throughChildren.toArray()andChildren.map()are no longer reported; only elements returned by.map()callbacks are checked; literal keys are no longer overwritten by later keys; and.map()calls on array literals with at most one element are skipped. (#2108)react-x/no-duplicate-key: the fast-path text check now matches barekeyattributes and keys separated from=by whitespace (ex:<div key />,<div key = {id} />), so such elements are no longer silently skipped.react-x/no-missing-component-display-name:memocomponents passed to generic HOCs are recognized, so anonymous ones require a display name. (#2084)react-x/no-missing-context-display-name: the autofix now applies to exported contexts and no longer produces invalid syntax for multi-declarator declarations. (#2088, #2089)react-x/no-missing-key: elements with a spread attribute are no longer reported as missingkey, and TypeScript-wrapped iterator callbacks are unwrapped before checking. (#2086, #2088)react-x/no-nested-component-definitions: array pattern element defaults andmemopropsAreEqualcomparators are no longer reported as nested components; optional-chainedcreateElementreturns are recognized. (#2084)react-x/no-unstable-context-valueandreact-x/no-unstable-default-props: shadowedBoolean(),String(), andNumber()calls are no longer reported. (#2089)react-x/no-unused-class-component-members: statically resolvable computed member reads and destructuring are counted as usages. (#2088)react-x/refs: non-null guards whose terminating branch is atrystatement, an all-terminatingswitchwith adefaultclause, or an all-terminatingwhile (true)/for (;;)/do...whileloop are now recognized, so ref writes reached only when the ref is null are no longer reported. (#2093, #2109)react-x/set-state-in-effect: TypeScript-wrapped setups are resolved; zero-argument setters called directly in the setup are reported; timer or event callbacks nested inuseCallback/useEffectEventare no longer treated as synchronous setters; every possible setter is reported when the callee may resolve to more than one; the ref-derived exemption applies to any argument position of a custom state hook's setter; ref-derived early-return guards gate the following statements insidetry/switch/bare blocks and loop bodies or update clauses; ref provenance follows IIFEs; nested and outer effect setups are analyzed independently; and setter calls reached through the same effect-side trigger are reported once per setter name. (#2075, #2082, #2083)react-x/static-components: the render-boundary check now requires that at least one declaration of the component binding lives inside a render body, instead of only checking the first declaration. (#2110)react-x/static-components: static components wrapped byuseMemooruseCallback(ex:useMemo(() => External, [])) are no longer reported; the memoized value is traced instead of the hook call itself. (#2113, closes #1762) Thanks to @itisrmk!react-x/use-state: calls in computed object property keys and JSX subtrees are now detected by the lazy-initialization check. (#2080)react-jsx/no-children-prop-with-children:childrensupplied through a statically resolvable computed key in acreateElementprops object is now detected. (#2086)react-jsx/no-children-prop:childrensupplied through a statically resolvable computed key in acreateElementprops object is now detected, and the suggestion to movechildreninto element content is no longer offered when a following spread attribute could override it. (#2086, #2102)react-jsx/no-leaked-semicolon: leaked semicolons between a JSX child and its parent's closing tag on the same line are now detected. (#2102)react-jsx/no-useless-fragment: fragments with a spread attribute are no longer reported, and lone-CR whitespace, including&#​13;, is treated as formatting padding like LF and CRLF. (#2086, #2092)react-dom/no-dangerously-set-innerhtml-with-children: empty expression containers and comment-only children no longer count as children; lone-CR whitespace, including&#​13;, no longer counts either. (#2086, #2092)react-dom/no-hydrateandreact-dom/no-render: autofixes now skip calls with extra or spread arguments and calls whose return values are used, and no longer prepend the new import at the top of the file — existing imports are reused, duplicates are skipped, and new imports are placed after file-level directives, header comments, and existing imports. (#2103, #2104)react-dom/no-script-url: namespaced attributes such asxlink:hrefare now checked forjavascript:URLs. (#2086)react-dom/no-unsafe-iframe-sandbox:sandboxpermissions are matched as whole whitespace-separated tokens, fixing false positives likesandbox="not-allow-scripts". (#2112)react-dom/no-unsafe-target-blank: the suggestion for a missingrelattribute now inserts it after the last JSX attribute, so a spread attribute cannot override the suggested value. (#2086)react-dom/no-use-form-state: autofix-added imports now reuse existing imports, avoid duplicates, and follow file-level directives, header comments, and existing imports. (#2104)react-dom/no-void-elements-with-children: comment-only/empty containers, newline-only formatting whitespace, and lone-CR whitespace, including&#​13;, no longer count as children. (#2086, #2092)react-web-api/no-leaked-event-listener: dot access and static computed access (including simple template-literal keys) now match as the same property; optional-chained listeners, event types, and receivers pair with their cleanup; string-literal and template-literal option keys are recognized; cyclicsignalalias chains no longer recurse forever; and function-parameter callees are no longer mistaken for the enclosing function. (#2085, #2092, #2093, #2100)react-web-api/no-leaked-fetch:signaloption keys written as string literals or simple template literals are recognized. (#2093)react-web-api/no-leaked-intersection-observerandreact-web-api/no-leaked-resize-observer:observe(...)andunobserve(...)now pair on optional-chained elements. (#2093)react-debug/function-component: only the first argument ofmemo/forwardRefis treated as the wrapped component;propsAreEqualcomparators returning JSX are no longer reported, and functions in that position no longer inherit the surrounding binding or wrapper flags. Array pattern element defaults are no longer reported, and optional-chainedcreateElementreturns are recognized. (#2084)🪄 Improvements
Added fast-path text checks so rules skip AST traversal when their target term is absent from the file. (#2088)
Affected rules:
react-x/no-children-countreact-x/no-children-for-eachreact-x/no-children-mapreact-x/no-children-onlyreact-x/no-children-to-arrayreact-x/no-clone-elementreact-x/no-direct-mutation-statereact-x/no-implicit-childrenreact-x/no-implicit-keyreact-x/no-implicit-refreact-x/no-nested-lazy-component-declarationsreact-x/no-unused-class-component-membersJSX and
createElementrules no longer resolve spread props, since a spread's contents are unknown; only direct attributes and properties are inspected. (#2086)Affected rules:
react-x/no-missing-keyreact-jsx/no-children-propreact-jsx/no-children-prop-with-childrenreact-jsx/no-useless-fragmentreact-dom/no-dangerously-set-innerhtmlreact-dom/no-dangerously-set-innerhtml-with-childrenreact-dom/no-missing-button-typereact-dom/no-missing-iframe-sandboxreact-dom/no-string-style-propreact-dom/no-unsafe-iframe-sandboxreact-dom/no-unsafe-target-blankreact-dom/no-void-elements-with-childrenreact-x/no-unknown-property: attribute-tag, DOM-property, and standard-name lookups are cached per React version and resolved lazily. (#2086)react-x/set-state-in-effectandreact-x/set-state-in-render: setters are recognized only as the second element of auseStatearray destructuring; tuple-index access and object-pattern numeric keys are no longer detected. (#2075)📝 Documentation
eslint-plugin-react-jsx(#2102),eslint-plugin-react-dom(#2103),eslint-plugin-react-web-api, andeslint-plugin-react-x, and removed their next-step sections.react-jsx/no-comment-textnodes,react-jsx/no-key-after-spread, andreact-jsx/no-leaked-dollar. (#2102)noExplicitSpreadPropsrecipe to state that it provides no autofix. (#2089, #2107)🏗️ Internal
@eslint-react/ast,@eslint-react/core, and@local/testkit: added tests for AST tree types, core semantic interfaces, and type utilities.@eslint-react/ast: added theCollectandAnalyzenamespaces andTraverse.simpleTraverse;Analyze.isUnconditionallyTerminatingnow handlestrystatements, terminatingswitchstatements with adefaultclause, and terminatingwhile (true)/for (;;)/do...whileloops;Compare.isEqualnow comparesChainExpression, regex literals, and membercomputed/optionalflags;Collectnow traversesforinitializers and updates; renamedCheck.isConditionaltoCheck.isConditionalOrLoop; addedCheck.isArrayPatternElementDefault,Check.isObjectPatternElementDefault,Check.isLoopStatement, andExtract.getJSXName; improved private identifier handling; removed the general-purposeExtract.getMemberChain,Extract.getPropertyName,Extract.findProperty, andExtract.getAssignmentTargetshelpers in favor ofresolveAssignmentTargetsfrom@eslint-react/varand rule-local traversal. (#2080, #2083, #2084, #2086, #2092, #2093, #2099, #2100)@eslint-react/core: moved thecreateElementhelpers to@eslint-react/jsx; component detection now checks wrapper argument positions and unwraps chain expressions; improved render-method detection and qualified type names; narrowed the accepted node types of hook/component detection helpers. (#2075, #2077, #2084, #2099)@eslint-react/var: addedresolveOriginChain,isProvenanceEqual,hasDefault, andresolveAssignmentTargets; expandedresolveObjectTypeandcreateImportLookup, which now exposesisModuleBindinginstead ofhasNamespace; madeisValueEqualidentity-only (useisProvenanceEqualfor structural provenance); and removedresolveBindingTarget/BindingTarget, with binding targets now unwrapped inline. (#2085, #2086, #2088, #2100)@local/samples: hardened the sample rules. (#2107)@local/testkit: added averifyAndFixhelper for testing rules with autofixes. (#2078)eslintto10.14.0,typescript-eslintto8.72.1,nextto16.4.5,vitestto5.1.0,tsdownto0.23.7,nxto24.0.4,oxlintto1.91.0,viteto8.3.6,effectto4.1.2, and thefumadocspackages to16.18.0.react-x/static-componentsorigins; no behavioral changes.@typescript-eslint/typescript-estreedependency from@eslint-react/ast,@eslint-react/core,@eslint-react/var, andeslint-plugin-react-x. (#2080)inlinedDependenciesfield from the monorepo package configuration.New Contributors
Full Changelog: Rel1cx/eslint-react@v5.28.8...v5.30.0
react-hook-form/resolvers (@hookform/resolvers)
v7.0.6Compare Source
Bug Fixes
v7.0.5Compare Source
Bug Fixes
v7.0.4Compare Source
Bug Fixes
TanStack/router (@tanstack/router-plugin)
v1.169.0Compare Source
Minor Changes
#8855
446ce1b- Require Node^20.19.0 || >=22.12.0(was>=20.19), so the CommonJS builds can load ESM-only dependencies throughrequire(esm). Node 21 and Node 22.0–22.11 do not enable it by default, so they are no longer supported.#8851
d250819- Require Vite 6 or later: thevitepeer range is now>=6.0.0. Vite 5 is no longer supported.Patch Changes
1ba19a0- fix: webpack and Rspack production builds no longer put the code splitter's "will not be code-split" warning, with the route file's absolute path, into the client bundle when the build process'sNODE_ENVisn'tproduction. The bundler's mode decides, and a config withoutmodecounts as production, as it does for webpack and Rspack. The warning still prints in the build output.#8852
94f36c4- The esbuild plugin now throws whenautoCodeSplittingis enabled, andTanStackRouterCodeSplitterEsbuildthrows, instead of silently bundling every route without splitting. Route generation with esbuild is unchanged.#8856
533ca27- Remove the undocumentedplugin.hmr.styleoption and theHmrOptionstype. Each bundler entry now picks its own HMR runtime: the webpack and Rspack entries already forced'webpack', and on Vite,'webpack'broke route HMR.#8853
13b6256- Remove internal code-splitter APIs: thecodeSplittingOptions.compilerPluginsoption, and the root-entry exportsunpluginRouterCodeSplitterFactory,getObjectPropertyKeyName,CodeSplitCompilerPlugin,ReferenceRouteCompilerPlugin,ReferenceRouteCompilerPluginContextandVirtualRouteSplitNodeCompilerPluginContext.#8860
b5e2ac9- Source maps of split routes now point at the route file. On webpack and Rspack (including Rsbuild), a split component or shared code mapped to the wrong line, because unplugin's loader dropped the router plugin's map;unpluginnow requires^3.5.0, which keeps it. The maps of split and shared modules also name the route file itself instead of its?tsr-split/?tsr-sharedmodule id, so debuggers bind breakpoints set in the route file.#8870
f420d4a- Vite route HMR now writesimport.meta.hot.accept(out instead of calling it through ahotalias. Vite only treats a module as a hot boundary when the call is spelled out, so an edit of a route file no framework plugin accepts (a.tsroute file, or an app without@vitejs/plugin-react) reloaded the page instead of updating the route in place. With React HMR, a route file that declares its own top-levelhotbinding no longer fails to compile withDuplicate declaration "hot".Updated dependencies [
446ce1b,ad5b3b7,ff157f0]:glincker/thesvg (@thesvg/react)
v4.0.9Patch Changes
v4.0.8Patch Changes
#1543
7cb4edeThanks @thegdsks! - Add the Flags category and the new@thesvg/flagspackage: every ISO 3166-1 country plus regional flags (England, Scotland, Wales, Catalonia, the Basque Country, Galicia, the Valencian Community, the Balearic Islands, the Canary Islands, Corsica, Occitania, the EU and the UN), each in 4x3, square and circle, with per-flag React components, plain SVG modules, color palettes, search aliases andgetFlagForLocale.Flags are in the shared catalog (website, search, CLI, MCP, CDN) but are not bundled into
@thesvg/iconsor the framework packages. This is not a breaking change: flags were never shipped in those packages before, so their contents are unchanged. Their generators now read the catalog through one shared exclusion list. The CLI and MCP server point flag results at@thesvg/flags, and the MCP search lists exact code, number and emoji matches first and returns flag palettes.v4.0.7Patch Changes
v4.0.6Patch Changes
v4.0.5Patch Changes
vitejs/vite-plugin-react (@vitejs/plugin-react)
v6.3.0Compare Source
Make
reactCompilerPresetwork with@rolldown/plugin-babel'sparalleloption (#1549)reactCompilerPresetnow refers to its Babel preset by module path instead of by function, so it can be sent to worker threads.better-auth/better-auth (better-auth)
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](https://redirect.github.com/better-auth/better-auth/pull
Configuration
📅 Schedule: (in timezone Europe/London)
🚦 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.