Would TanStack Query try a pre-release check for TypeScript regressions?

[DrKoopz]

Hi Dominik and TanStack Query team,

I’m building Downstream CI, a small tool that type-checks the same example against a published npm package and a release candidate. The idea is to catch cases where an update would make existing user code stop compiling.

I saw the useQuery regression where checking data.type no longer let TypeScript narrow the result. Since that’s already fixed, I’d use it to test whether Downstream CI would have caught the break. If there’s a more recent case you’d rather protect, I’d be happy to use that instead. [Issue #11018](#11018)

Would you or another maintainer be open to a 15-minute pilot? I’d prepare the example and share a ready-to-run command. I’d like to know whether the result would be useful enough to run again before a release.

Thanks!