Skip to content

chore(deps): Update all non-major dependencies - #208

Merged
chertik77 merged 2 commits into
mainfrom
renovate/all-minor-patch
Nov 16, 2026
Merged

chertik77 merged 2 commits into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@better-auth/passkey (source) ^1.7.18 → ^1.7.22 age confidence
@eslint-react/eslint-plugin (source) ^5.28.8 → ^5.30.2 age confidence
@hookform/resolvers (source) ^7.0.3 → ^7.0.6 age confidence
@tanstack/router-plugin (source) ^1.168.48 → ^1.169.0 age confidence
@thesvg/react (source) ^4.0.4 → ^4.0.9 age confidence
@vitejs/plugin-react (source) ^6.2.1 → ^6.3.0 age confidence
better-auth (source) ^1.7.18 → ^1.7.22 age confidence
lucide-react (source) ^1.70.0 → ^1.72.0 age confidence
motion ^14.10.1 → ^14.13.0 age confidence
prettier (source) ^3.9.10 → ^3.10.1 age confidence
react-hook-form (source) 7.91.0 → 7.92.0 age confidence
steiger (source) ^0.9.0 → ^0.10.0 age confidence
typescript-eslint (source) ^8.72.1 → ^8.72.2 age confidence
vite (source) ^8.3.6 → ^8.3.8 age confidence

Release Notes

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

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

Rel1cx/eslint-react (@​eslint-react/eslint-plugin)

v5.30.2

Compare Source

🐞 Fixes
  • react-web-api/no-leaked-fetch: non-global fetch calls are no longer checked: a bare fetch(...) whose name is bound by an enclosing scope (ex: a local function fetch() {}) and member calls on non-global objects (ex: api.fetch(...)) are ignored, while window.fetch(...), globalThis.fetch(...), and self.fetch(...) are still recognized. (#​2116, closes #​2072)

Full Changelog: Rel1cx/eslint-react@v5.30.1...v5.30.2

v5.30.1

Compare 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
  • Removed the Vercel deploy step from the release workflow.

Full Changelog: Rel1cx/eslint-react@v5.30.0...v5.30.1

v5.30.0

Compare Source

✨ New
  • @eslint-react/eslint-plugin: added the all-type-checked preset, which extends all with the rules that require type information. (#​2095)
  • @eslint-react/eslint-plugin: added the experimental @eslint-react/unstable-exhaustive-deps rule, forked from exhaustive-deps, with a hooks option modeled on Biome's useExhaustiveDependencies (closureIndex/dependenciesIndex for custom Hooks, and stableResult for stable results). The rule lives in the unified plugin's own src/rules while incubating and is enabled in the all preset (and thereby in all-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, and useCallback/useMemo/useEffectEvent wrappers 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-chained createElement calls 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 through Children.toArray() and Children.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 bare key attributes 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: memo components 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 missing key, and TypeScript-wrapped iterator callbacks are unwrapped before checking. (#​2086, #​2088)
  • react-x/no-nested-component-definitions: array pattern element defaults and memo propsAreEqual comparators are no longer reported as nested components; optional-chained createElement returns are recognized. (#​2084)
  • react-x/no-unstable-context-value and react-x/no-unstable-default-props: shadowed Boolean(), String(), and Number() 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 a try statement, an all-terminating switch with a default clause, or an all-terminating while (true)/for (;;)/do...while loop 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 in useCallback/useEffectEvent are 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 inside try/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 by useMemo or useCallback (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: children supplied through a statically resolvable computed key in a createElement props object is now detected. (#​2086)
  • react-jsx/no-children-prop: children supplied through a statically resolvable computed key in a createElement props object is now detected, and the suggestion to move children into 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 &#&#8203;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 &#&#8203;13;, no longer counts either. (#​2086, #​2092)
  • react-dom/no-hydrate and react-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 as xlink:href are now checked for javascript: URLs. (#​2086)
  • react-dom/no-unsafe-iframe-sandbox: sandbox permissions are matched as whole whitespace-separated tokens, fixing false positives like sandbox="not-allow-scripts". (#​2112)
  • react-dom/no-unsafe-target-blank: the suggestion for a missing rel attribute 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 &#&#8203;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; cyclic signal alias 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: signal option keys written as string literals or simple template literals are recognized. (#​2093)
  • react-web-api/no-leaked-intersection-observer and react-web-api/no-leaked-resize-observer: observe(...) and unobserve(...) now pair on optional-chained elements. (#​2093)
  • react-debug/function-component: only the first argument of memo/forwardRef is treated as the wrapped component; propsAreEqual comparators 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-chained createElement returns 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-count
    • react-x/no-children-for-each
    • react-x/no-children-map
    • react-x/no-children-only
    • react-x/no-children-to-array
    • react-x/no-clone-element
    • react-x/no-direct-mutation-state
    • react-x/no-implicit-children
    • react-x/no-implicit-key
    • react-x/no-implicit-ref
    • react-x/no-nested-lazy-component-declarations
    • react-x/no-unused-class-component-members
  • JSX and createElement rules 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-key
    • react-jsx/no-children-prop
    • react-jsx/no-children-prop-with-children
    • react-jsx/no-useless-fragment
    • react-dom/no-dangerously-set-innerhtml
    • react-dom/no-dangerously-set-innerhtml-with-children
    • react-dom/no-missing-button-type
    • react-dom/no-missing-iframe-sandbox
    • react-dom/no-string-style-prop
    • react-dom/no-unsafe-iframe-sandbox
    • react-dom/no-unsafe-target-blank
    • react-dom/no-void-elements-with-children
  • react-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-effect and react-x/set-state-in-render: setters are recognized only as the second element of a useState array destructuring; tuple-index access and object-pattern numeric keys are no longer detected. (#​2075)

📝 Documentation
  • Added a TanStack Redact example and updated the website's community projects list. (#​2079)
  • Added known-issues references for eslint-plugin-react-jsx (#​2102), eslint-plugin-react-dom (#​2103), eslint-plugin-react-web-api, and eslint-plugin-react-x, and removed their next-step sections.
  • Documented known limitations and workarounds for react-jsx/no-comment-textnodes, react-jsx/no-key-after-spread, and react-jsx/no-leaked-dollar. (#​2102)
  • Synced the migration tables with rule features and updated the configuration and third-party plugin docs. (#​2106)
  • Synced the website recipe snippets with the hardened sample rules, and corrected the noExplicitSpreadProps recipe to state that it provides no autofix. (#​2089, #​2107)
  • Updated the FAQ, glossary, examples pages, the contributing guide's monorepo architecture diagram and package/example listings, and the term-based rule implementation patterns.
🏗️ 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 the Collect and Analyze namespaces and Traverse.simpleTraverse; Analyze.isUnconditionallyTerminating now handles try statements, terminating switch statements with a default clause, and terminating while (true)/for (;;)/do...while loops; Compare.isEqual now compares ChainExpression, regex literals, and member computed/optional flags; Collect now traverses for initializers and updates; renamed Check.isConditional to Check.isConditionalOrLoop; added Check.isArrayPatternElementDefault, Check.isObjectPatternElementDefault, Check.isLoopStatement, and Extract.getJSXName; improved private identifier handling; removed the general-purpose Extract.getMemberChain, Extract.getPropertyName, Extract.findProperty, and Extract.getAssignmentTargets helpers in favor of resolveAssignmentTargets from @eslint-react/var and rule-local traversal. (#​2080, #​2083, #​2084, #​2086, #​2092, #​2093, #​2099, #​2100)
  • @eslint-react/core: moved the createElement helpers 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: added resolveOriginChain, isProvenanceEqual, hasDefault, and resolveAssignmentTargets; expanded resolveObjectType and createImportLookup, which now exposes isModuleBinding instead of hasNamespace; made isValueEqual identity-only (use isProvenanceEqual for structural provenance); and removed resolveBindingTarget/BindingTarget, with binding targets now unwrapped inline. (#​2085, #​2086, #​2088, #​2100)
  • @local/samples: hardened the sample rules. (#​2107)
  • @local/testkit: added a verifyAndFix helper for testing rules with autofixes. (#​2078)
  • Bumped dependencies across the workspace, including eslint to 10.14.0, typescript-eslint to 8.72.1, next to 16.4.5, vitest to 5.1.0, tsdown to 0.23.7, nx to 24.0.4, oxlint to 1.91.0, vite to 8.3.6, effect to 4.1.2, and the fumadocs packages to 16.18.0.
  • Collapsed multi-line expressions in react-x/static-components origins; no behavioral changes.
  • Enforced a 1-day dependency maturity period; served README assets from the jsDelivr CDN; restricted website deployments to stable releases via a Vercel deploy hook; refactored the publish workflow trigger and pinned zizmor through its official action.
  • Removed the ko-fi sponsorship and funding configuration.
  • Removed the now-unused @typescript-eslint/typescript-estree dependency from @eslint-react/ast, @eslint-react/core, @eslint-react/var, and eslint-plugin-react-x. (#​2080)
  • Removed the unused inlinedDependencies field from the monorepo package configuration.
  • Unified test language options and reorganized the test harness: tsconfig fixtures replace the per-JSX-emit tester factories, and untyped parsing disables typescript-estree's single-run inference. (#​2105)
  • Unwrapped multi-line comments to single lines across packages, plugins, and scripts; no behavioral changes.
New Contributors

Full Changelog: Rel1cx/eslint-react@v5.28.8...v5.30.0

react-hook-form/resolvers (@​hookform/resolvers)

v7.0.6

Compare Source

Bug Fixes
  • arktype: report object-level issues on the empty path (#​895) (e02dcd6)
  • valibot: clear native validation errors after successful validation (#​896) (b02b258)

v7.0.5

Compare Source

Bug Fixes

v7.0.4

Compare Source

Bug Fixes
  • valibot: report object-level issues on the empty path (#​893) (451b1cf)
TanStack/router (@​tanstack/router-plugin)

v1.169.0

Compare 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 through require(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: the vite peer 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's NODE_ENV isn't production. The bundler's mode decides, and a config without mode counts as production, as it does for webpack and Rspack. The warning still prints in the build output.

  • #​8852 94f36c4 - The esbuild plugin now throws when autoCodeSplitting is enabled, and TanStackRouterCodeSplitterEsbuild throws, instead of silently bundling every route without splitting. Route generation with esbuild is unchanged.

  • #​8856 533ca27 - Remove the undocumented plugin.hmr.style option and the HmrOptions type. 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: the codeSplittingOptions.compilerPlugins option, and the root-entry exports unpluginRouterCodeSplitterFactory, getObjectPropertyKeyName, CodeSplitCompilerPlugin, ReferenceRouteCompilerPlugin, ReferenceRouteCompilerPluginContext and VirtualRouteSplitNodeCompilerPluginContext.

  • #​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; unplugin now 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-shared module id, so debuggers bind breakpoints set in the route file.

  • #​8870 f420d4a - Vite route HMR now writes import.meta.hot.accept( out instead of calling it through a hot alias. 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 .ts route 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-level hot binding no longer fails to compile with Duplicate declaration "hot".

  • Updated dependencies [446ce1b, ad5b3b7, ff157f0]:

glincker/thesvg (@​thesvg/react)

v4.0.9

Patch Changes
  • feat: flags in the packages menu and extensions, no repo link on flag pages (#​1548)

v4.0.8

Patch Changes
  • #​1543 7cb4ede Thanks @​thegdsks! - Add the Flags category and the new @thesvg/flags package: 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 and getFlagForLocale.

    Flags are in the shared catalog (website, search, CLI, MCP, CDN) but are not bundled into @thesvg/icons or 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.7

Patch Changes
  • fix: update deepgram brand color to E042FF (#​1541)

v4.0.6

Patch Changes
  • feat: add icons for projects that use thesvg (#​1535)

v4.0.5

Patch Changes
  • feat: add gong symbol variant (#​1531)
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.3.0

Compare Source

Make reactCompilerPreset work with @rolldown/plugin-babel's parallel option (#​1549)

reactCompilerPreset now 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.22

Compare Source

Patch Changes

v1.7.21

Compare Source

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

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

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

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

  • [#​12179](https://redirect.github.com/better-auth/better-auth/pull

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


Configuration

📅 Schedule: (in timezone Europe/London)

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

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


  • 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 added the dependencies Pull requests that update a dependency file label Nov 16, 2026
@vercel

vercel Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
task-pro Ready Ready Preview Nov 16, 2026 8:24pm UTC

@chertik77
chertik77 force-pushed the renovate/all-minor-patch branch from d21cdf2 to 7f03d9b Compare November 16, 2026 20:24
@chertik77
chertik77 merged commit 4ace59f into main Nov 16, 2026
3 checks passed
@chertik77
chertik77 deleted the renovate/all-minor-patch branch November 16, 2026 20:26

This branch was successfully deployed

1 active deployment
Preview — 7f03d9b4 Deployed Nov 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant