chore(deps): update dependencies minor and patch updates - #474
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/minor-patch
branch
8 times, most recently
from
September 1, 2026 12:43
8993a6f to
ed5586d
Compare
renovate
Bot
force-pushed
the
renovate/minor-patch
branch
6 times, most recently
from
September 10, 2026 02:36
a2fbaba to
bd68dc9
Compare
renovate
Bot
force-pushed
the
renovate/minor-patch
branch
5 times, most recently
from
September 13, 2026 17:26
eb18d11 to
c153c1e
Compare
renovate
Bot
force-pushed
the
renovate/minor-patch
branch
from
September 14, 2026 02:10
c153c1e to
dc6ec54
Compare
|
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:
1.162.1→1.162.45.102.4→5.102.81.170.32→1.170.361.19.0→1.20.026.4.0→26.4.219.2.8→19.3.019.2.8→19.3.07.86.0→7.88.017.0.12→17.0.144.4.3→4.6.5Release Notes
TanStack/router (@tanstack/history)
v1.162.4Compare Source
Patch Changes
#8359
8fff7fa- Normalize memory history hrefs consistently with browser and server history, including protocol-relative paths and control characters.#8352
f021f6d- Avoid temporary arrays when replacing forward memory-history entries.#8349
ae68535- Avoid generating unused history keys for locations with existing state.#8354
9872d2a- Use lightweight request history for SSR and make server navigation a no-op. Use redirect() to issue HTTP redirects. Server hrefs use the same normalization as browser history to handle protocol-relative URLs and control characters.v1.162.3Compare Source
Patch Changes
#8308
9c1871c- Validate navigation and redirect destinations, keep ambiguous relative URLs on the current origin, and constrain prerender requests and output paths. Prevent redirect headers from appearing in serialized server function response bodies.Preserve native form HTTP redirects, route error handling and masks for document redirects, and per-navigation destinations for shared loader redirects. Avoid redundant origin parsing and reduce link styling and server-rendering work. Configured origins must already be normalized.
Keep blocked-link inactive props consistent during React hydration, honor explicit redirect Location headers before checking route options, and refresh Vue link state when destinations become internal. Reuse the protocol-relative URL check while parsing redirect schemes once.
Reduce React link bundle size by sharing pathname comparisons, state-prop selection, and element creation.
Share normalized pathname comparisons in Solid and Vue links to reduce bundle size.
#8287
0654c0a- Use full-document navigation when an output rewrite produces a cross-origin destination, including the public URL of a route mask.Respect registered history blockers during document navigation, passing history locations and the requested push or replace action.
v1.162.2Compare Source
Patch Changes
#8264
9035abc- RespectignoreBlockerduringgo()navigation, including document unload warnings. Preserve beforeunload warnings during back and forward navigation unlessignoreBlockeris requested, and clear the bypass after same-document traversal so later document navigation still warns about unsaved changes.Restore the original browser history entry when forward or multi-entry navigation is blocked.
TanStack/query (@tanstack/react-query)
v5.102.8Compare Source
Patch Changes
v5.102.7Compare Source
Patch Changes
v5.102.6Compare Source
Patch Changes
#11305
ac2b612- fix(react-query): throw falsy errors fromuseQueriesanduseSuspenseQueriesto the error boundaryUpdated dependencies []:
v5.102.5Compare Source
Patch Changes
578e5c2]:TanStack/router (@tanstack/react-router)
v1.170.36Compare Source
Patch Changes
#8390
b747fb8- Keep the Link location cache out of server bundles:buildLocationonly creates, reads and writes it whenisServeris false. Render React Links on the server without the extra prop copies and the forwarded-ref hook. Link SSR rendering is 20-40% faster in the Link benchmarks and the React Start SSR request loop about 7% faster.React
activePropsandinactivePropsnow follow one precedence rule on every link, including links whose destination is blocked for using a disallowed scheme: state props override element props,refand event handlers, whilehref,disabledandtargetstay controlled by the router. Previously a blocked link ignored arefor handler from its inactive props.React
LinkanduseLinkPropssplit router options from element props with one key set on the client and the server. Element props pass through as given: external links forward them verbatim, falsy values included, anduseLinkPropsnow returnschildrenfor router-controlled links as it already did for external ones.#8324
6387d58- Reuse hydration snapshot getters to avoid unnecessary store-instance effect updates when Links and other hydration-aware components rerender.#8318
9b2adaf- Allow active and inactive Link props to override base element props in React and Solid while preserving class/style merging. Keep React'shref,target, anddisabledvalues controlled by routing options. Preserve Vue object and nested-array class bindings, including reactive updates and server rendering, without mutating cached bindings during VNode normalization.#8327
634da91- MakepathParamsAllowedCharactersinitialization-only. Configure it when creating the router; changing allowed characters requires a new router instance. Remove decoder-update bookkeeping and decoder-change checks from route-owned path caches.#8370
e9396c9- Stop exporting the internalisPlainObjectandisPlainArrayhelpers.#8324
6387d58- Avoid a redundant prop copy when rendering native Links while preserving custom-component props and the public hook result.#8252
7e349c3- Reduce the bundle cost of shared Link pathname interpolation while preserving its rendering performance. Reuse one interpolation pass for pathname and optional metadata, keep the bounded cache on the router, and simplify React Link active-state and prop merging.#8370
e9396c9- Reuse built locations for Links whose destination does not depend on the current location.buildLocationkeeps the result per options object when the build never read the current location, and the ReactLinkpasses one stable options object per instance, so navigations resolve unchanged Links with a lookup instead of a full build. The per-route pathname interpolation cache this replaces is removed. Linkparams,searchandactiveOptionsare compared by value on render, so inline object literals with unchanged contents keep reusing the Link's location. Pass a new object to change a destination; like any other React prop, an object mutated in place is not re-read.Updated dependencies [
d76a332,b747fb8,6cfb1e8,700a714,700a714,8fff7fa,f021f6d,ae68535,7e349c3,873c830,7e349c3,634da91,e9396c9,634da91,f151ab0,bc57fa3,9872d2a,d76a332,634da91,634da91,7e349c3,9448caa,e9396c9,700a714,634da91,634da91]:v1.170.35Compare Source
Patch Changes
8c43c71- Upgrade TanStack Store to 0.11 and migrate router subscriptions to useSelector, preserving selector comparisons and Vue subscription cleanup.v1.170.34Compare Source
Patch Changes
#8279
aee42c6- Avoid allocating event-handler arrays and wrapper functions for links without user-supplied event handlers.#8308
9c1871c- Validate navigation and redirect destinations, keep ambiguous relative URLs on the current origin, and constrain prerender requests and output paths. Prevent redirect headers from appearing in serialized server function response bodies.Preserve native form HTTP redirects, route error handling and masks for document redirects, and per-navigation destinations for shared loader redirects. Avoid redundant origin parsing and reduce link styling and server-rendering work. Configured origins must already be normalized.
Keep blocked-link inactive props consistent during React hydration, honor explicit redirect Location headers before checking route options, and refresh Vue link state when destinations become internal. Reuse the protocol-relative URL check while parsing redirect schemes once.
Reduce React link bundle size by sharing pathname comparisons, state-prop selection, and element creation.
Share normalized pathname comparisons in Solid and Vue links to reduce bundle size.
#8311
9aec5a7- React Links resolve state props without temporary class-name arrays or unnecessary style copies.Updated dependencies [
f9836f1,9c1871c,9871c06,0654c0a]:v1.170.33Compare Source
Patch Changes
#8165
2f20c00- Exclude structural descendants below error and not-found boundaries from route lifecycle callbacks. Preserve lifecycle membership through invalidation, hydration, background reloads, and superseded navigation publication.#8209
28a5e45- Preserve falsy thrown values in React and Vue error boundaries. Type React and Vue boundary error components andonCatchcallbacks asunknown. Solid boundary errors remain typed asError; SSR now wraps non-Errorloader errors to match Solid’s native boundary behavior, preserving the original value incause. Router state and loaderonErrorvalues are unchanged.When upgrading React or Vue, narrow boundary errors (for example, with
error instanceof Error) before readingmessageorstack.ErrorComponentProps<TError>remains available for values narrowed to a specific error type. RouteonErrortypes are unchanged.#8161
f0b5eda- Retain successful not-found matches as terminal shared boundaries during client navigation, preserving route context while the destination loads.#8251
0497cae- Use URL.canParse for absolute URL checks in links, navigation, redirects, and build configuration. Preserve a URL constructor fallback for older browsers.#8169
0caf6b9- Fix route-scopeduseMatch,useSearch, anduseParamsAPIs to forward theshouldThrowoption and preserve optional return types whenshouldThrow: false.#8257
cf166d1- Fix repeatedinnerHTMLwrites for unchanged styles and data scripts during React re-renders. This prevents unnecessary CSS parsing and Trusted Types errors during client navigation.Updated dependencies [
edf0e16,2f20c00,28a5e45,08eff50,216c0c4,2f91503,f0b5eda,50eafca,0497cae,ee28348,9035abc,c18e690]:axios/axios (axios)
v1.20.0Compare Source
v1.20.0 — August 19, 2026
This release hardens runtime option handling, adds RFC 9110 status-code aliases, fixes Node.js and XHR reliability issues, and refreshes project tooling and documentation.
🔒 Security Fixes
🐛 Bug Fixes
🔧 Maintenance & Chores
🌟 New Contributors
We are thrilled to welcome our new contributors. Thank you for helping improve axios:
Full Changelog (axios/axios@v1.19.0...v1.20.0)
i18next/i18next (i18next)
v26.4.2Compare Source
$&,$`,$'and$$inside a nested value ($t(key)) now stay literal.nest()handed the resolved value straight toString.replaceas the replacement argument, so those sequences were read as replacement patterns:$&re-inserted the$t(...)match,$`/$'inserted the text before / after it, and$$collapsed to$. Throught()the$&case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted$t(...)was matched again on every pass andt()never returned — also under the defaultescapeValue: truewhen the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" })with a name containing$&). The value is now$-escaped at theString.replacecall, the same guardinterpolate()already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @mahirhir (#2447).v26.4.1Compare Source
keyPrefixoverload ofgetFixedT()is now available underenableSelector: 'strict'. Its constraint was gated ontrue | 'optimize'only, so under'strict'it collapsed tonever, the overload dropped out, and the returnedtsilently lost itskeyPrefixscope (t(($) => $.deep)failed withProperty 'deep' does not exist on type '{}'). The same call already typechecked undertrueand'optimize'. Thanks @hovelopin (#2446).react/react (react)
v19.3.0Compare Source
react/react (react-dom)
v19.3.0Compare Source
react-hook-form/react-hook-form (react-hook-form)
v7.88.0: Version 7.88.0Compare Source
✨ Features
🐞 Fixes
resetField()(#13735)replace()(#13734)reset()duringhandleSubmit()(#13733)trigger()targets their parent (#13732)handleSubmit()(#13731)trigger()targets a field with only nested resolver errors (#13730)useWatchcompute cache not being initialized with the initial output (#13728)FileListbeing lost during flatten/expand and omit undefined values injsonToFormData(#13725)schemaErrorLookupreporting nested containers as exact-name errors (#13727)isValidatingnot being recomputed afterunregister()clears validating fields (#13723)reset()(#13722)iterateFieldsByActiononly breaking out of one loop level (#13718)setError()overwrites (#13716)reset()not clearing validating fields (#13714)remove()leaking deleted values onto surviving field-array items (#13713)validateFieldcallingsetCustomValidityonce per key in validate-object mode (#13707)useFieldArrayfocus behavior for checkboxes and radio buttons in appended rows (#13705)getFieldStatereadingisValidatingfrom the supplied form state (#13704)unregister()stripping kept values from the submit payload (#13703)useFormStatenot re-subscribing when control changes (#13702)reset()keepingdirtyFieldsout of sync withisDirtywhenkeepValuesis enabled (#13701)useFormnot reconciling correctly when an Activity subtree is initially hidden (#13698)delayErrortimer fires (#13697)cloneObjectthrowing when checkingBlobwithinstanceof(#13694)useFieldArrayretaining stale fields after an Activity subtree reconnects (#13688)🧹 Refactors
_isTrackedto the remaining multi-key proxy/subscribe form-state checks (#13699)_isTrackedhelper for proxy/subscribe form-state checks (#13690)abortEarlyparameter fromiterateFieldsByAction(#13689)clearErrors(#13696)📝 Documentation
useWatchcompute example variable names in JSDoc (#13700)📦 Dependencies
joifrom 18.2.1 to 18.2.5 (#13719)❤️ Thank You
v7.87.0Compare Source
Added
shouldTouchoption fortrigger()OpaqueTypesregistry for opaque leaf typesFixed
useController().field.onChange()-like APIsControllerunder a null parent submittingundefinedinstead of a valueERR_MODULE_NOT_FOUNDresolvingreact-hook-formdue to areact-serverdeclaration (Next.js builds)useWatchnever reconciling when anActivitysubtree is hidden on its first renderresetFieldnot recomputingisValidfor subscribe-only consumersgenerateWatchOutputignoringdefaultValuefor an array of namesuseFormStatenever reconciling when anActivitysubtree is hidden on its first renderi18next/react-i18next (react-i18next)
v17.0.14Compare Source
i18nobject returned byuseTranslationwas only refreshed wheni18n.languagechanged, so aresolvedLanguage(orlanguages) change of its own kept handing components the previous snapshot. That happens whenever the translations for the current language arrive after the switch — i18next resolves to the fallback until its store has them — and components readingi18n.resolvedLanguage(language switchers, for example) then stayed one switch behind. The cached wrapper is now keyed on all three language fields, which are exactly the ones the surroundinguseMemoalready depends on; wrapper identity still only changes when the language state does, so the caching from #1885 is unaffected. Reported via next-i18next#2348.v17.0.13Compare Source
keyPrefixoverload ofuseTranslation()is now available underenableSelector: 'strict'.useTranslationwas gated ontrue | 'optimize'only, so under'strict'it resolved to the legacy signature and the selector overload disappeared entirely (keyPrefix: ($) => $.ns.foofailed withType '($: any) => any' is not assignable to type 'undefined').Transalready handled all three modes. Companion to the same fix forgetFixedTin i18next#2446. Thanks @hovelopin (#1930).colinhacks/zod (zod)
v4.6.5Compare Source
Commits:
d2b135cdocs: add the 4.6.x patch highlights to the 4.6 postf1448f7docs: fold the 4.6.x patch highlights into the 4.6 post's own sectionsde65a5cdocs: lead the properties section with the check and add a Zod Mini tab (#6598)56222cdfeat(instanceof): key the .properties() shape off the instance type (#6600)ca0229aRevert "feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)"cc4cd4eRevert "Revert "feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)""0f3f5ee4.6.559bbc03chore: re-pin the integration peers to the workspace zod after the 4.6.5 bumpv4.6.4Compare Source
A patch on top of 4.6.3.
d6bc1e30feat: addz.currencyCode()over a vendored ISO 4217 list, refreshed weekly by CI (#6595)ad32d751perf:z.url()rejects an invalid URL withURL.canParse()instead of a throwing constructor, about 50x faster; fewer allocations on the validation path (#6588)2bb08717chore: re-pin the integration peers to the workspace zod after the 4.6.4 bumpf6e1701achore(deps): bump next to 15.5.25 and vite to 7.3.6 (#6153)v4.6.3Compare Source
A patch on top of 4.6.2.
413cce9afix(v4): make z.properties() a check again (#6594) — removes the standalonez.properties()schema from 4.6.0;z.instanceof().properties()and.check(...z.properties())are unchanged75d63ee1docs: show only the.properties()method form in the 4.6 post46da9572docs: match the error-message examples to what the parsers emitv4.6.2Compare Source
Commits:
a00c3f3docs: use Trigger.dev's brand-kit lockups for the platinum card0c483c5docs: Zod 4.6 announcement post (#6546)9446b5cfix: preserve undefined prefault outputs and object keys (#6587)e359f734.6.2v4.6.1Compare Source
A patch on top of 4.6.0.
b12aa523fix: preserve unique tags with defaulted discriminators (#6582) — closes #6577dd9c36fafix(v4): defer recursive object index inference (#6580)3b154992feat(lang): add Tajik (tg) locale (#6581) by @ismoil772efa8b80ci: give the npm wait a real budget and drop the back-publish path (#6583)v4.6.0Compare Source
Commits:
908c9e1fix(docs): retry the GitHub stars fetch and log the real status93186cadocs(wiki): drop the zod-compiler benchmark (#6505)8ce9e8dfeat(mini): publish Zod Mini as the standalone @zod/mini package (#6491)2956c4cchore(mini): sync @zod/mini to 4.5.4abd41addocs(wiki): move plans and comparisons into a gitignored internal/ (#6506)8106573chore(docs): build with Turbopackc7ec94dci: check zod and @zod/mini lockstep on npm after every publish (#6507)c46eeffchore: narrow blanket biome-ignore comments (#6504)a0898b4ci: wait hours for npm to serve a publish, not ten minutes (#6502)1c0bce0docs: bring the 4.5 charts and worked examples into the docs pages70eb2c0docs: drop the traits section and the compilation feature bullet43b9bfcdocs: drop the bound-methods section from the Zod package pagecd4f9a6perf(v4): report Standard Schema issues without constructing a ZodError (#6509)f3cb364docs: surface the blog on the home page and in the sidebarf3e7c72fix(docs): render the docs 404 page inside the (doc) layout oncef412178ci: publish @zod/mini to JSR in lockstep with npm (#6510)5ff9566Stop re-exporting the compile internals from zod/v4/core (#6511)40b4d0bfix(ci): read zod's latest version with npm view when picking the backfill dist-taga6b4939Mark the compile internals @internal instead of hiding them (#6518)3195ed0docs: label the memory chart like the compile chart8cd1250docs: center the memory chart callout labelsff56a55docs: center the memory chart callout labels and pad them off the numberfb2fedfdocs: tighten the memory chart callout, pad the canvas, say "less memory"93f3ab3docs: replace the blog navbar's GitHub icon with a star-count pill7ae49d6docs: drop the circle around the star pill's GitHub mark and center it on the pill's arcb801439bench: add typebox (compiled and dynamic) to the moltar cross-library harness1ec6b7cdocs: add an RSS feed to the blog at /blog/rss.xml08ba069perf(v4): read Luhn digits with charCodeAt instead of string indexing (#6529)319f47fEmit a length-aware base64url pattern in toJSONSchema (#6527)a2a019aAccept enum-typed targets in z.toZod (#6528)74f9a6ddocs: drop the toZod enum block from basics and pin the page's curation rule in a commentf83ab51fix(v4): rejectConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.