Skip to content

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

Merged
chertik77 merged 1 commit into
mainfrom
renovate/all-minor-patch
Oct 19, 2026
Merged

chertik77 merged 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@better-auth/passkey (source) ^1.7.7 → ^1.7.10 age confidence
@eslint-react/eslint-plugin (source) ^5.24.10 → ^5.28.0 age confidence
@radix-ui/react-roving-focus (source) ^1.1.20 → ^1.2.1 age confidence
@tanstack/eslint-plugin-query (source) ^5.104.1 → ^5.104.3 age confidence
@tanstack/react-query (source) ^5.104.1 → ^5.104.3 age confidence
@tanstack/react-router (source) 1.170.42 → 1.170.44 age confidence
@tanstack/router-plugin (source) ^1.168.43 → ^1.168.46 age confidence
@thesvg/react (source) ^3.3.13 → ^3.4.0 age confidence
better-auth (source) ^1.7.7 → ^1.7.10 age confidence
chrono-node ^2.10.2 → ^2.10.3 age confidence
lucide-react (source) ^1.55.0 → ^1.58.0 age confidence
motion ^14.1.0 → ^14.3.0 age confidence
react (source) ^19.3.0 → ^19.3.1 age confidence
react-dom (source) ^19.3.0 → ^19.3.1 age confidence
react-hook-form (source) 7.89.0 → 7.90.0 age confidence
typescript-eslint (source) ^8.71.1 → ^8.71.2 age confidence

Release Notes

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

v1.7.10

Compare Source

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.
Rel1cx/eslint-react (@​eslint-react/eslint-plugin)

v5.28.0

Compare Source

✨ New
  • @eslint-react/eslint-plugin: the general-purpose presets now enable JSX syntax support via languageOptions.parserOptions.ecmaFeatures.jsx: true, so you no longer need to configure it yourself. (#​2049) Affected presets:
    • recommended
    • recommended-typescript
    • recommended-type-checked
    • strict
    • strict-typescript
    • strict-type-checked
🏗️ Internal
  • Bumped fumadocs-core and fumadocs-ui to 16.17.5, and lucide-react to 1.58.0.

Full Changelog: Rel1cx/eslint-react@v5.27.4...v5.28.0

v5.27.4

Compare Source

🐞 Fixes
  • @eslint-react/jsx: resolveAttributeValue now handles a parser-tolerated JSXFragment in attribute value position (ex: <a href=<></> />), reporting it as kind "element" instead of falling through to undefined; as a result, react-dom/no-missing-iframe-sandbox now reports <iframe sandbox=<></> /> instead of silently skipping it. (#​2048)

Full Changelog: Rel1cx/eslint-react@v5.27.3...v5.27.4

v5.27.3

Compare Source

🐞 Fixes
  • react-jsx/no-key-after-spread: the fast-path text check now matches key assignments with whitespace around = (ex: <div {...props} key = {id} /> or a newline before =), so such elements are no longer silently skipped. (#​2043) Thanks to @​amir-rahmanii!
  • react-jsx/no-children-prop: a children prop alongside nested children content (ex: <div children="x">y</div>, createElement("div", { children: "x" }, "y")) is no longer reported by this rule — that conflict case belongs to react-jsx/no-children-prop-with-children — removing the unsafe merge suggestion and the duplicate diagnostics. (#​2044) Thanks to @​amir-rahmanii!
  • react-jsx/no-children-prop-with-children: empty expression containers (ex: {}, {/* comment */}) are no longer treated as meaningful children, so <div children="x">{/* comment */}</div> is no longer reported. (#​2045) Thanks to @​amir-rahmanii!
📝 Documentation
  • react-naming-convention/ref-name: corrected the additionalRefHooks example to use the /pattern/flags RegExp string form; a bare (a|b) string is treated as exact equality and never matches. (#​2042) Thanks to @​amir-rahmanii!
  • The settings docs examples for the additional hooks settings now use full RegExp strings. (#​2047)
🏗️ Internal
  • @eslint-react/jsx: hasChildren now treats empty expression containers as non-meaningful, aligned with getChildren. (#​2045)
  • react-x: refactored the internals of set-state-in-effect, set-state-in-render, and static-components for readability; no behavior change. (#​2041)
  • Bumped vitest to 5.0.5, next to 16.4.2, fumadocs-core and fumadocs-ui to 16.17.4, and undici to 8.12.2.

Full Changelog: Rel1cx/eslint-react@v5.27.2...v5.27.3

v5.27.2

Compare Source

🏗️ Internal
  • Added the missing @tsconfig/node20 and @types/node dependencies to the workspace packages. (#​2040)
  • Bumped effect and @effect/platform-node to 4.0.5, import-integrity-lint to 1.3.1, and sort-package-json to 4.1.0. (#​2040)

Full Changelog: Rel1cx/eslint-react@v5.27.1...v5.27.2

v5.27.1

Compare Source

🐞 Fixes
  • Lifecycle methods defined as class properties (ex: componentDidMount = () => { this.setState(...) }, including type-expression-wrapped values) are now reported just like the method shorthand form. (#​2039) Affected rules:
    • react-x/no-set-state-in-component-did-mount
    • react-x/no-set-state-in-component-did-update
    • react-x/no-set-state-in-component-will-update
  • Effect cleanups are now recognized when the useEffect call is nested in an outer return (ex: return useEffect(() => () => { ... })), so resources released there are no longer reported as leaked. (#​2039) Affected rules:
    • react-web-api/no-leaked-event-listener
    • react-web-api/no-leaked-fetch
    • react-web-api/no-leaked-intersection-observer
    • react-web-api/no-leaked-interval
    • react-web-api/no-leaked-resize-observer
    • react-web-api/no-leaked-timeout
🏗️ Internal
  • @eslint-react/ast: added the Check.isFunctionOrClass and Check.isTypeOrChainExpression helpers; parent lookups across ast, core, and the rules are now bounded at enclosing function/class boundaries. (#​2039)
  • @eslint-react/core: isUseEffectSetupCallback and isUseEffectCleanupCallback reimplemented on bounded parent lookups. (#​2039)

Full Changelog: Rel1cx/eslint-react@v5.27.0...v5.27.1

v5.27.0

🐞 Fixes
  • react-web-api/no-leaked-event-listener: cleanups returned through conditional expressions (ex: return cond ? () => window.removeEventListener(...) : null) are now recognized and no longer reported. (#​2038)
  • react-web-api/no-leaked-fetch: effect setups wrapped in type expressions (ex: useEffect((() => { fetch(...) }) as any, [])) are now recognized. (#​2038)
  • react-debug/function-component: computed string-literal displayName keys (ex: App["displayName"] = "...") are now recognized. (#​2038)
📝 Documentation
  • Revised the rule implementation pattern guides and refined the core ideas and layer dependency model in the fact-based rule implementation docs. (#​2034, #​2035)
🏗️ Internal
  • @eslint-react/core: accuracy and consistency fixes in detection helpers. (#​2038)
  • react-x: the custom tsl config now enforces the fact-based layer dependency order. (#​2036)
  • Bumped react and react-dom to 19.3.1, and next to 16.4.1.

Full Changelog: Rel1cx/eslint-react@v5.26.7...v5.27.0

v5.26.7

Compare Source

🏗️ Internal
  • @eslint-react/core: collectors now use the node's source range start as the map key, replacing the shared counter, keys are stable across repeated lints, traceable to source positions when debugging, and slightly cheaper than stringified numbers. (#​2033)

Full Changelog: Rel1cx/eslint-react@v5.26.6...v5.26.7

v5.26.6

Compare Source

🏗️ Internal
  • @eslint-react/core: component and hook collectors now use sequential integer keys instead of random randomBytes hex keys, removing node:crypto from the lint hot path. (#​2032) Thanks to @​kurtextrem!
  • Bumped effect to 4.0.4, ts-pattern to 5.9.2, fumadocs-core and fumadocs-ui to 16.17.3, lucide-react to 1.57.0, oxlint to 1.88.0, typedoc-plugin-markdown to 4.14.0, and undici to 8.12.1.
New Contributors

Full Changelog: Rel1cx/eslint-react@v5.26.5...v5.26.6

TanStack/query (@​tanstack/eslint-plugin-query)

v5.104.3

Compare Source

No changes in this release.

v5.104.2

Compare Source

No changes in this release.

TanStack/query (@​tanstack/react-query)

v5.104.3

Compare Source

Patch Changes

v5.104.2

Compare Source

Patch Changes
TanStack/router (@​tanstack/react-router)

v1.170.44

Compare Source

Patch Changes

v1.170.43

Compare Source

Patch Changes
TanStack/router (@​tanstack/router-plugin)

v1.168.46

Compare Source

Patch Changes
glincker/thesvg (@​thesvg/react)

v3.4.0

Compare Source

Minor Changes
  • #​1326 cd0d0eb Thanks @​thegdsks! - Brand families and 150+ new icons. theSVG now groups products by owner (Amazon, Google, Microsoft, Apple, Meta, Adobe and more) with a page per family, and the packages gain a large batch of self-hosted apps, cloud native projects and integration brands, refreshed marks, and corrected default colours for icons that were white-only.

v3.3.15

Compare Source

Patch Changes
  • feat: brand families, OG screenshots and asset refresh (replay of #​1322) (#​1323)

v3.3.14

Compare Source

Patch Changes
better-auth/better-auth (better-auth)

v1.7.10

Compare Source

Patch Changes
  • #​11393 eebd47a Thanks @​breken-ai! - If you use the lastLoginMethod plugin with oneTap, signing in through Google One Tap now records "google", the same value as signing in with the Google button. Before, a One Tap sign-in recorded nothing: the better-auth.last_used_login_method cookie kept its previous value or stayed unset, and so did user.lastLoginMethod with storeInDatabase.

    If your customResolveMethod includes a /one-tap/callback → "google" workaround, remove that mapping; keep the resolver if it handles other routes.

  • #​11821 09d07e6 Thanks @​gustavovalverde! - The Google One Tap prompt (authClient.oneTap() without button) no longer calls getSkippedReason(), which Google's FedCM migration guide says to remove. Before, it called it under any promptOptions.fedCM setting.

    A skipped prompt now ends the flow and calls onPromptNotification right away instead of retrying. Google doesn't report why a prompt was skipped, and a prompt the user closed stays hidden for Google's cooldown period, so the retries could not bring it back. Dismissed prompts still retry as before.

    Google Identity Services still logs its FedCM migration warning, because it does so whenever prompt() receives a listener. The plugin needs the listener to track dismissals and skips, so the warning is expected and safe to ignore.

  • #​11819 eaecb72 Thanks @​gustavovalverde! - Google One Tap now applies your socialProviders.google.mapProfileToUser and custom getUserInfo, the same as the standard Google sign-in. Before, One Tap ignored both and always stored the token's name, email, email_verified, and picture claims.

    If you configured either one, users created through One Tap now get the fields it returns, including any extra fields such as a first name from given_name. Returning users are updated from it on each One Tap sign-in when socialProviders.google.overrideUserInfoOnSignIn is on, and so are existing users that One Tap links when account.accountLinking.updateUserInfoOnLink is on. Check that your mapper suits One Tap users too.

    If you set socialProviders.google.overrideUserInfoOnSignIn, One Tap sign-ins now update returning users' name, image, and email from Google, as the redirect sign-in already does.

    Setups that configure none of these, including oneTap({ clientId }) with no Google provider, are unaffected.

  • #​11820 88c9a37 Thanks @​gustavovalverde! - If you set autoSelect or cancelOnTapOutside on oneTapClient(), the One Tap prompt and the Sign in with Google button now use them. Before, only values passed to authClient.oneTap() took effect, so with autoSelect: true on the plugin, returning users still had to pick an account. Values passed to oneTap() still override the plugin's. Apps that set these options only on oneTap(), or not at all, are unaffected.

  • #​11696 0cf1f7c Thanks @​drewsephski! - You can now import the One Tap plugin from better-auth/plugins/one-tap, as you can for other plugins. Previously this import failed with a "not exported" error. Imports from better-auth/plugins and better-auth/client/plugins are unchanged.

  • #​11822 414e845 Thanks @​gustavovalverde! - You can now import the Captcha and OpenAPI plugins from better-auth/plugins/captcha and better-auth/plugins/open-api, as you can for other plugins. Previously these imports failed with a "not exported" error. Imports from better-auth/plugins are unchanged.

    If your TypeScript config uses "moduleResolution": "node" (or node10), better-auth/plugins/multi-session and better-auth/test now resolve their types. Previously TypeScript reported that it could not find their declarations. Projects using bundler, node16, or nodenext resolution are unaffected.

  • Updated dependencies [fedd055, bbd0a19, 99cdfe7]:

v1.7.9

Compare Source

Patch Changes

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.

  • #​11565 b1cfc1e Thanks @​bytaesu! - Omit non-returned custom fields from inferred output schema types.

  • #​11540 678c555 Thanks @​bytaesu! - Align cookie security attributes with RFC 6265bis.

  • #​10591 193efff Thanks @​kdelay! - Expired or revoked sessions now clear stale cookies when using customSession.

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

  • #​11391 352d04c Thanks @​breken-ai! - Fix customSession treating session lookup failures as signed-out users. Server-side getSession now throws an API error, and HTTP clients receive an error response.

  • #​11750 e9d9921 Thanks @​gustavovalverde! - Generic OAuth providers configured with discoveryUrl now recover without a restart when discovery fails at startup. Since 1.7.3, a provider whose discovery request failed at boot (for example, because the identity provider was still starting) was skipped, and every sign-in returned PROVIDER_NOT_FOUND until the app restarted. Better Auth now retries discovery on the next sign-in, callback, or account-linking request for that provider, and the provider works as soon as discovery succeeds. While discovery keeps failing, sign-in and account linking still return PROVIDER_NOT_FOUND and callbacks redirect with error=oauth_provider_not_found, and each request may wait up to 10 seconds for the retry.

  • #​11549 1bd5c37 Thanks @​bytaesu! - Fix lastLoginMethod failing sign-in when cookieName or maxAge is explicitly undefined.

  • #​11174 766cfb3 Thanks @​Bekacru! - Stop double-decoding callbackURL, newUserCallbackURL and errorCallbackURL on magic link verify so percent-encoded characters in callback query params are preserved.

  • #​11505 c46992f Thanks @​bytaesu! - Preserve the referenced model and field keys when generating Kysely migrations, so custom table names that match another model key produce the intended foreign keys.

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

  • #​10266 c68b2cd Thanks @​shiminshen! - Projects that enable exactOptionalPropertyTypes can use the oauthProvider() and mcp() plugins again. Since 1.7.0, adding either plugin to betterAuth() failed to type-check with a TS2322 error.

  • #​11637 2627237 Thanks @​gustavovalverde! - Projects using the organization plugin with skipLibCheck: false no longer get TS2536: Type '"role"' cannot be used to index type ... from crud-members.d.mts. The role returned by getActiveMemberRole is now typed as the organization's role names directly. Projects with skipLibCheck: true (the default in most templates) were unaffected.

  • #​10866 3d1f008 Thanks @​heliohm! - The organization plugin no longer pulls every zod locale into server bundles.

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

  • #​10698 f0ce580 Thanks @​jashkarangiya! - If you set the phone number plugin's verifyOTP option, /phone-number/reset-password now checks the code with it, as /phone-number/verify already does. Before, password reset always compared the code with the one Better Auth generated, so apps that verify codes through a provider such as Twilio Verify could not reset passwords. If your sendPasswordResetOTP sends the code Better Auth generates, make sure verifyOTP accepts that code. Apps that don't set verifyOTP are unaffected.

  • #​11646 07a0938 Thanks @​gustavovalverde! - A failed password reset no longer spends the reset link or OTP. /reset-password, /email-otp/reset-password and /phone-number/reset-password now check the token or code without consuming it, validate and hash the new password, then consume it in the same transaction as the session revocation and password write. A rejected password, such as one refused by haveIBeenPwned, always leaves the link or OTP usable. A later failure, such as a failed session revocation or password write, also leaves it usable when the adapter's transactions are enabled and verification values are stored in the database (the default without secondary storage, or verification.storeInDatabase: true). Wrong codes still count against the OTP attempt limit.

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

  • #​11488 e15625f Thanks @​Bekacru! - SvelteKit 3 projects can now install Better Auth without --legacy-peer-deps. The @sveltejs/kit peer range now includes ^3.0.0; SvelteKit 2 projects are unaffected.

  • Updated dependencies [4175b34, 435645e, 369176e, 0cfe07d, 9904b29, e78f15a, 60525e0, 8133265, ea85d13, 916ef5c, 1d95ebf, 6214610, 67743ed, c46d2a6, 92dfcea, a9f455d, 9725f1b]:

lucide-icons/lucide (lucide-react)

v1.58.0: Version 1.58.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.57.0...1.58.0

v1.57.0: Version 1.57.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.56.0...1.57.0

motiondivision/motion (motion)

v14.3.0

Compare Source

Added
  • stagger: New grid, from: "edges" | "random" options.
  • Support for scaleZ.
Fixed
  • Fix matrix3d and other digit-named transform functions being tokenised as numbers.
  • useSpring: Ensure when switching targets we animate to the new target on switch.
  • Fix SVG MotionValue children being written as a children attribute.

v14.2.0

Compare Source

Added
  • Hardware accelerated independent transforms like x, y, scaleX etc.
react/react (react)

v19.3.1: 19.3.1 (October 14th, 2026)

Compare Source

React Server Components

react-hook-form/react-hook-form (react-hook-form)

v7.90.0

Compare Source

Changed
  • Improve performance of watch, subscribe, scoped subscriptions, dirty field checks and form state fan-out
  • Reduce bundle size
Fixed
  • Fields named after Object.prototype members not being marked as touched on blur and setValue
  • Dirty values extraction for fields named hasOwnProperty
  • cloneObject dropping the length of sparse arrays
  • cloneObject failing on objects with a null prototype
  • Form options removed from props on re-render not being reset
  • remove() mishandling duplicated indexes and mutating the indexes passed in
  • useFieldArray unregistering fields while a parent array reindexes
  • Input edited before the form is ready being overwritten
  • useWatch not updating watched objects after an <Activity> subtree reconnects
  • useWatch preferring its own defaultValue over form defaultValues for array names
  • reset without values and keepDefaultValues setting isDirty to true
  • Controller blur validation not working after reset
  • watch reading a stale shouldUnregister option when a field registers
  • Native validation reading a stale shouldUseNativeValidation option when stopping at the first error
  • Form values stored under a ref key not being compared correctly
  • setError, clearErrors and remaining error updates not producing a new errors reference

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 Oct 19, 2026
@vercel

vercel Bot commented Oct 19, 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 Oct 19, 2026 9:54am UTC

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 75d5d6f to b3bec2f Compare October 19, 2026 09:53
@chertik77
chertik77 merged commit b5695ed into main Oct 19, 2026
4 checks passed
@chertik77
chertik77 deleted the renovate/all-minor-patch branch October 19, 2026 13:57

This branch was successfully deployed

1 active deployment
Preview — b3bec2fc Deployed Oct 19, 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