Repository navigation
chore: update Start fixture dependencies - #1
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (9)
📒 Files selected for processing (16)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe repository and Start fixtures update TanStack Router and Start versions. Site-start fixtures change TypeScript aliases and provenance records. The npm lock-conflict test now reads package data from a dedicated fixture. ChangesTanStack Start dependency updates
npm lock-conflict test fixture
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to The fixture refresh keeps the intended dependency versions and provenance, and the lock-conflict test retains its asserted cases. No concrete merge-blocking regression was found. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 4 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Update the Start fixture inputs to React Start 1.168.60 and React Router 1.170.41.
The root dependency graph, browser fixture generator, and eight install/site fixture lockfiles use the published patch versions. The four site fixture manifests and source hashes are refreshed from Router main at d35aab425b07b46e222a507c0f0239644669757b, retaining their declared portable substitutions.
The native npm conflict control now reads a small npm-generated lock fragment from the previous committed graph. This keeps the same conflict assertions when the current graph deduplicates Babel.
Validation: npm ci, browser Start fixture generation with 95 integrity-verified archives, all 45 source-check CI tests on Node 24, 32 installer/persistence tests, and eight fixture/provenance tests passed. Two unrelated WASM toolchain tests skipped because their tools are not installed. The complete SDK build is still unavailable in this clean checkout: its kernel-builtin preparation needs fixtures/workloads/node_modules/sql.js. Browser/native SDK acceptance was not run. This is a source fixture refresh, with no deployment or SDK release.
Summary by CodeRabbit
Updates
Tests