[aicayzer]

Summary

Moves @tanstack/react-start to 1.169.3 and @tanstack/react-router to 1.170.45 together, and switches the one server function to the renamed .validator() method. This supersedes #516, which bumped Start alone to 1.168.60: that release depends on Router 1.170.41 exactly while this repository pinned 1.170.40, so two Router copies were installed and the Start type augmentation landed on the wrong one. Every route's server: option then failed type-checking (TS2353) and Build and type-check failed.

Changes

• package.json and pnpm-lock.yaml: @tanstack/react-start 1.168.59 to 1.169.3, @tanstack/react-router 1.170.40 to 1.170.45 (the exact version Start 1.169.3 depends on). @tanstack/react-router-devtools is unchanged: it declares Router as a range peer dependency, which 1.170.45 satisfies.
• src/routes/$.tsx: createServerFn(...).inputValidator(...) becomes .validator(...). Start removed the deprecated .inputValidator() in start-client-core 1.170.36 (it takes the same validator), and the build failed to prerender /overview without this change.

Testing

• pnpm install, then pnpm why @tanstack/react-router: one version (1.170.45) installed.
• pnpm build: passes, 319 pages prerendered. pnpm build:status: passes.
• pnpm types:check: passes for both targets.
• pnpm test: 28 files, 366 tests pass.
• pnpm dev, then fetched /llms.txt, /api/search?query=key, /api/docs/search?q=key, /api/docs/topics, /docs-map.md, /overview and /overview.md (all 200 with expected content), and a tools/list request to /mcp (returns the tool list).
• Not tested: the deployed Workers.

Notes for reviewers

• Start 1.169 is a minor release whose changelog is only dependency updates, but the .inputValidator() removal landed in the start-client-core range it now depends on, so it is a real breaking change for this repository. No other use of it exists in src/.
• The repository sets no dependency maturity gate. Both chosen versions were published on 16 October 2026, more than the three days Dependabot requires.
• Review depth: dependency bump with one mechanical rename, no change to content or the published API.

Checklist

• The title is a scoped Conventional Commit.
• New behavior has a test that was seen failing first, or no test was needed and the reason is above. No new behavior: the existing build, type check and tests cover the bump and the rename.
• Docs, comments and the contract still say what is true after this change.

[aicayzer]

Review: checks only