Bump the react-and-ui group with 3 updates

[dependabot]

Bumps the react-and-ui group with 3 updates: @cloudflare/kumo, @tanstack/react-router and @tanstack/router-plugin.

Updates @cloudflare/kumo from 2.12.0 to 2.13.1

Release notes

Sourced from @​cloudflare/kumo's releases.

@​cloudflare/kumo@​2.13.1

Patch Changes

• 7d5241d: Allow default Tooltip trigger children to control their line height, preventing inherited text from being clipped.

@​cloudflare/kumo@​2.13.0

Minor Changes

• 4066307: Add unknown-total pagination support through hasNextPage.
• f74936f: Add Toolbar.Link, which renders a LinkButton with toolbar sizing, styling, and keyboard navigation.

Patch Changes

• d004940: Position dialogs near the top of the viewport instead of vertically centering them.

• 8f0a1f0: Use the elevated surface color for even rows in the default Table variant.

• 1ede8bf: fix(select): align the trigger surface with form controls

  Select triggers now use bg-kumo-control, including their open and disabled states, so they match Input, Combobox, and the rest of the form-control family. Consumer background classes can still override the default without using !important. The popup remains on the floating bg-kumo-base surface.

• 8482c50: fix(select): anchor the popup below the trigger and expose placement props

  Select.Positioner relied on Base UI's alignItemWithTrigger default (true), which overlays the popup on the trigger so the selected option's text lands on the trigger's value text, emulating a native <select>. Options always render at text-base, so on xs/sm triggers the popup was much taller than its anchor, and Base UI's compensating shift detached it from the trigger — on xs it overhung by 12.5px above and 45.5px below and sat 8px to the left, covering adjacent content.

  The popup now prefers bottom placement and is offset from the trigger, with Base UI's collision avoidance still flipping it automatically when the preferred side lacks space. Placement is configurable:

  prop	default	notes
  side	"bottom"	preferred side; still flips automatically on collision
  sideOffset	4	gap between trigger and popup, matching Combobox/Autocomplete
  align	"start"	alignment along the trigger edge
  alignOffset	—	additional offset along the alignment axis
  alignItemWithTrigger	false	opt back in to the native <select> overlay

  The remaining Base UI Positioner controls are also forwarded unchanged: anchor, arrowPadding, positionMethod, collisionAvoidance, collisionBoundary, collisionPadding, sticky, and disableAnchorTracking.

... (truncated)

Changelog

Sourced from @​cloudflare/kumo's changelog.

2.13.1

Patch Changes

• 7d5241d: Allow default Tooltip trigger children to control their line height, preventing inherited text from being clipped.

2.13.0

Minor Changes

• 4066307: Add unknown-total pagination support through hasNextPage.
• f74936f: Add Toolbar.Link, which renders a LinkButton with toolbar sizing, styling, and keyboard navigation.

Patch Changes

• d004940: Position dialogs near the top of the viewport instead of vertically centering them.

• 8f0a1f0: Use the elevated surface color for even rows in the default Table variant.

• 1ede8bf: fix(select): align the trigger surface with form controls

  Select triggers now use bg-kumo-control, including their open and disabled states, so they match Input, Combobox, and the rest of the form-control family. Consumer background classes can still override the default without using !important. The popup remains on the floating bg-kumo-base surface.

• 8482c50: fix(select): anchor the popup below the trigger and expose placement props

  Select.Positioner relied on Base UI's alignItemWithTrigger default (true), which overlays the popup on the trigger so the selected option's text lands on the trigger's value text, emulating a native <select>. Options always render at text-base, so on xs/sm triggers the popup was much taller than its anchor, and Base UI's compensating shift detached it from the trigger — on xs it overhung by 12.5px above and 45.5px below and sat 8px to the left, covering adjacent content.

  The popup now prefers bottom placement and is offset from the trigger, with Base UI's collision avoidance still flipping it automatically when the preferred side lacks space. Placement is configurable:

  prop	default	notes
  side	"bottom"	preferred side; still flips automatically on collision
  sideOffset	4	gap between trigger and popup, matching Combobox/Autocomplete
  align	"start"	alignment along the trigger edge
  alignOffset	—	additional offset along the alignment axis
  alignItemWithTrigger	false	opt back in to the native <select> overlay

  The remaining Base UI Positioner controls are also forwarded unchanged: anchor, arrowPadding, positionMethod, collisionAvoidance, collisionBoundary, collisionPadding, sticky, and disableAnchorTracking.

... (truncated)

Commits

• 2c1cbed Version Packages (#774)
• 7d5241d fix(tooltip): prevent nested text clipping (#773)
• a5800aa Version Packages (#747)
• b094a5a fix(combobox): align popup input with content edges (#768)
• 1ede8bf fix(select): align trigger with input surfaces (#758)
• 20b7880 fix(input-group): tighten large addon button inset (#767)
• f74936f feat(toolbar): add Toolbar.Link (#757)
• 4066307 feat(pagination): support unknown totals (#752)
• 7526a6a fix(text): inherit line height for non-heading variants (#749)
• d004940 feat(dialog): position dialogs near viewport top (#748)
• Additional commits viewable in compare view

Updates @tanstack/react-router from 1.170.32 to 1.170.33

Changelog

Sourced from @​tanstack/react-router's changelog.

1.170.33

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 and onCatch callbacks as unknown. Solid boundary errors remain typed as Error; SSR now wraps non-Error loader errors to match Solid’s native boundary behavior, preserving the original value in cause. Router state and loader onError values are unchanged.

  When upgrading React or Vue, narrow boundary errors (for example, with error instanceof Error) before reading message or stack. ErrorComponentProps<TError> remains available for values narrowed to a specific error type. Route onError types 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-scoped useMatch, useSearch, and useParams APIs to forward the shouldThrow option and preserve optional return types when shouldThrow: false.

• #8257 cf166d1 - Fix repeated innerHTML writes 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]:

  • @​tanstack/router-core@​1.171.28
  • @​tanstack/history@​1.162.2

Commits

• a58e01c ci: Version Packages (#8182)
• 08eff50 fix(router-core): fix dangling references in published declarations (#8207)
• cf166d1 fix(react-router): avoid rewriting unchanged head assets (#8257)
• 07b3bc9 test(react-router): cover pending and not-found context (#8243)
• 2f20c00 fix(router-core): skip lifecycle callbacks below fallback boundaries (#8165)
• 0497cae perf(router): use URL.canParse for absolute URL checks (#8251)
• 28a5e45 fix(router): handle unknown error boundary values (#8209)
• f0b5eda fix(router-core): retain not-found boundary during navigation (#8161)
• 0caf6b9 fix: preserve shouldThrow in route-scoped hooks (#8169)
• See full diff in compare view

Updates @tanstack/router-plugin from 1.168.35 to 1.168.36

Release notes

Sourced from @​tanstack/router-plugin's releases.

@​tanstack/router-plugin@​1.168.36

Patch Changes

• Updated dependencies [edf0e16, 2f20c00, 28a5e45, 08eff50, 216c0c4, 2f91503, f0b5eda, 50eafca, 0497cae, 0caf6b9, ee28348, cf166d1, c18e690]:
  • @​tanstack/router-core@​1.171.28
  • @​tanstack/react-router@​1.170.33
  • @​tanstack/router-generator@​1.167.34

Changelog

Sourced from @​tanstack/router-plugin's changelog.

1.168.36

Patch Changes

• Updated dependencies [edf0e16, 2f20c00, 28a5e45, 08eff50, 216c0c4, 2f91503, f0b5eda, 50eafca, 0497cae, 0caf6b9, ee28348, cf166d1, c18e690]:
  • @​tanstack/router-core@​1.171.28
  • @​tanstack/react-router@​1.170.33
  • @​tanstack/router-generator@​1.167.34

Commits

• a58e01c ci: Version Packages (#8182)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

---

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.