Release frequency and regression testing concerns

[cdeutsch]

First off, thanks for all the work going into TanStack Router — it’s great to see how quickly it’s evolving.

I wanted to ask about the current release cadence. There seem to be multiple releases per day, and it’s been a bit hard to keep up. I’m finding that I can’t even get PRs reviewed as fast as new versions are being published.

For example, I recently had to submit a PR to fix an encoding issue that completely broke links. That kind of regression feels like something that might benefit from a bit more testing time before release.

Totally understand the desire to move fast, but I wonder if slowing releases slightly or adding more pre-release testing could help catch issues like this while still keeping momentum.

[cdeutsch]

I just had to revert yet another @tanstack/react-router patch upgrade because of the significant rewrite that happened in 1.170.19.

This isn't the first patch release where that's happened.

Could reworks like this land in a major instead? A lot of setups auto-merge patch bumps, so anything non-trivial in them reaches production before anyone's had a chance to review it.

/cc @Sheraff