Written by Huifer, solo developer and maintainer of TanStack Ship. React Query is the layer I touch most often in client work, so a version bump in the 5.x line is never a five-minute job in my templates: the React package, the framework-agnostic core, the devtools, and the persister all have to agree on a version. When 5.106.0 landed, I pulled the published tarballs for 5.105.3 and 5.106.0 and diffed them file by file before touching a lockfile.
Verified sources: TanStack · TanStack Query docs ·
@tanstack/react-query5.106.0 on npm · TanStack Query on GitHub · web.dev · Cloudflare Workers docsLast updated: 2026-11-05 · Changelog
@tanstack/react-query 5.106.0 was published to npm on 2026-11-04 at 20:13:09Z and carries the latest dist-tag. It is a minor bump from 5.105.3 (2026-11-02). The important finding is not the version number: I diffed the published tarballs, and the @tanstack/react-query and @tanstack/query-core builds are byte-identical to 5.105.3 — only package.json changed, for the version string and the exact pin on @tanstack/query-core@5.106.0. 5.106.0 is a version-alignment release; the functional work in this window landed in 5.105.1 and 5.105.2.
TL;DR
- Measured:
@tanstack/react-query5.106.0 published2026-11-04T20:13:09.653Zwith thelatesttag; the previous version 5.105.3 published2026-11-02T20:39:13.878Z.- Measured: zero changed files in the published
build/of@tanstack/react-querybetween 5.105.3 and 5.106.0 — 410 files in both tarballs.- Measured:
@tanstack/react-query@5.106.0depends on@tanstack/query-core@5.106.0— an exact pin, not a caret range.- Calculated: seven TanStack Query packages published between
20:12:02Zand20:13:09Z— a 67-second release train.- Measured: the code changes in this window landed in 5.105.1 (289 core files differ vs 5.105.3), 5.105.2 (143), and 5.105.3 (99).
- My call: bump it, but upgrade the family together and re-run your cache-behaviour smoke test — nothing about 5.106.0 requires code changes on your side.
Short answer:
@tanstack/react-query5.106.0 is the 2026-11-04 minor release of TanStack Query's React hooks package and npm'slatesttag. Its published build is byte-identical to 5.105.3 — a version-alignment release that re-pins@tanstack/query-coreto 5.106.0, so no API migration is required.
TanStack Query 5.106.0: What Changed and How to Upgrade
This guide is for two people: the developer with @tanstack/react-query in a lockfile and an upgrade ticket, and the founder choosing a SaaS starting point who wants to know whether the data layer in a template is actually maintained. If you are in the first group, the upgrade checklist is the part you want. If you are in the second, read Which template capability this release supports and skip the rest.
Everything here is measured against the published npm tarballs and registry metadata, not against a changelog summary — because for this release there is no changelog in the registry payload, and the interesting story only appears when you diff the artifacts.
What 5.106.0 Actually Is: A Version-Alignment Release
What the npm record proves
The registry entry for 5.106.0 is the source of truth. Here is what it says:
| Registry field | Value in @tanstack/react-query@5.106.0 |
|---|---|
| Version | 5.106.0 (previous: 5.105.3, published 2026-11-02) |
| Publish timestamp | 2026-11-04T20:13:09.653Z |
| Description | "Hooks for managing, caching and syncing asynchronous and remote data in React" |
| License | MIT |
| Repository | git+https://github.com/TanStack/query.git (directory packages/react-query) |
| Runtime dependency | @tanstack/query-core: 5.106.0 — pinned exactly, not a caret range |
| Peer dependencies | react: ^18 || ^19, @types/react: ^18 || ^19 (optional) |
| Entry points | build/modern/index.js (ESM) and build/legacy/index.cjs (CJS), plus a ./@tanstack/custom-condition subpath export |
sideEffects | false |
| Published files | 410 |
| Other dist-tags | previous: 4.44.0, plus alpha, beta, rc tags still pointing at 5.0.0 prereleases |
The dependency row is the one that matters operationally: @tanstack/react-query pins @tanstack/query-core to the exact same version. There is no caret range to fall back on, which is good — you cannot accidentally end up with a 5.105 core under a 5.106 React package unless your lockfile was hand-edited.
What the published artifacts prove
Here is the part I could not find written down anywhere, so I measured it by downloading both tarballs and diffing them:
# Compare the two published builds of the React package
mkdir -p /tmp/rq-diff && cd /tmp/rq-diff
npm pack @tanstack/react-query@5.105.3 --silent
npm pack @tanstack/react-query@5.106.0 --silent
mkdir -p old new
tar -xzf tanstack-react-query-5.105.3.tgz -C old
tar -xzf tanstack-react-query-5.106.0.tgz -C new
diff -rq old/package/build new/package/build | wc -l # -> 0
diff -rq old/package new/package | wc -l # -> 1 (package.json only)
Zero files differ inside build/. The only difference in the entire package is package.json, and inside it only two lines: the version string, and the @tanstack/query-core pin moving from 5.105.3 to 5.106.0. I ran the same diff against @tanstack/query-core itself: again, package.json is the only changed file.
That makes 5.106.0 a version-alignment release. Nothing in the shipped code changed relative to 5.105.3, so there is no new API to adopt and no behaviour to migrate — but the version number moved, and the whole family moved with it.
Where the Real Changes Landed: Inside the 5.105.x Line
If you jumped from 5.104.x or older straight to 5.106.0, the code you are actually adopting is three releases old. The line was busy in the eight days before 5.106.0:
| Core package comparison | Files that differ |
|---|---|
| 5.105.0 → 5.105.1 | 289 |
| 5.105.1 → 5.105.2 | 143 |
| 5.105.2 → 5.105.3 | 99 |
| 5.105.3 → 5.106.0 | 1 (package.json only) |
The React wrapper followed the same shape: 304 files differ in its build/ between 5.105.0 and 5.105.3, and none between 5.105.3 and 5.106.0. The published .d.ts files in the core changed across that range too — 23 declaration files differ between 5.105.0 and 5.105.3, covering queryClient, queryObserver, mutation, hydration, focusManager, onlineManager, timeoutManager, and others.
Why this matters if you are upgrading from 5.104.x or older: the interesting review work is in 5.105.1 through 5.105.3, not in 5.106.0. If you skim only the newest release notes you will miss the release that actually contained the code. Review the range, not the tag.
The Coordinated Release Train: Seven Packages in 67 Seconds
The family moved together on 2026-11-04:
| Package | Version | Timestamp (UTC) |
|---|---|---|
@tanstack/query-sync-storage-persister | 5.106.0 | 20:12:02 |
@tanstack/query-devtools | 5.106.0 | 20:12:19 |
@tanstack/react-query-devtools | 5.106.0 | 20:12:22 |
@tanstack/react-query-persist-client | 5.106.0 | 20:12:23 |
@tanstack/query-core | 5.106.0 | 20:12:34 |
@tanstack/query-persist-client-core | 5.106.0 | 20:12:38 |
@tanstack/react-query | 5.106.0 | 20:13:09 |
The exact-pin rule for @tanstack/query-core
Because the React package pins the core exactly, and because devtools and persister packages carry their own matching versions, a partial bump is the only realistic failure mode here. A tree with @tanstack/react-query@5.106.0 and @tanstack/react-query-devtools@5.105.3 will install cleanly — the devtools package is not a peer dependency — and the mismatch only shows up as odd devtool behaviour.
One command confirms the tree is coherent:
npm ls @tanstack/react-query @tanstack/query-core @tanstack/react-query-devtools
npm outdated --filter @tanstack/react-query
If you want the check to run in CI rather than in someone's terminal, this is the whole guard:
// scripts/check-query-versions.ts — run in CI before a deploy
import { readFileSync } from 'node:fs'
const pkg = JSON.parse(readFileSync('package.json', 'utf8'))
const deps = { ...pkg.dependencies, ...pkg.devDependencies }
const react = deps['@tanstack/react-query']
const core = deps['@tanstack/query-core']
const devtools = deps['@tanstack/react-query-devtools']
const versions = new Set([react, core, devtools].filter(Boolean))
if (versions.size > 1) {
console.error('TanStack Query family out of sync:', { react, core, devtools })
process.exit(1)
}
console.log('TanStack Query family aligned:', react)
The Upgrade Checklist for a React Query App
Step 1 — Bump the family in one commit
Change the version, then let npm resolve the family from the same release window rather than trusting a stale lockfile:
{
"dependencies": {
"@tanstack/react-query": "5.106.0",
"@tanstack/query-core": "5.106.0"
},
"devDependencies": {
"@tanstack/react-query-devtools": "5.106.0"
}
}
Commit the lockfile with it. A version bump that lives in package.json but not in the lockfile is not an upgrade.
Step 2 — Check the peer range and the bundler entry points
The peer range is react: ^18 || ^19, so React 18 and 19 are both in scope. The package ships sideEffects: false and exposes both a modern ESM build and a legacy CJS build, plus a ./@tanstack/custom-condition subpath export. If your bundler resolves the legacy build — a Vite resolve.mainFields override, a Jest moduleNameMapper, or a Node build without exports support — you will silently keep using the CJS entry. Check your bundler config if you are moving from an older install.
Step 3 — Re-verify the five behaviours that actually break apps
This release changes no behaviour, so use it as a good moment to re-verify the things that break SaaS dashboards in practice:
| Behaviour to re-verify | What to check | Official reference |
|---|---|---|
| Query key stability | Every key still maps to one request; no key factory returning a new object per render | Query keys |
| Freshness and garbage collection | staleTime and gcTime defaults still match what your UI assumes | Important defaults |
| Invalidation scope | invalidateQueries still targets the right keys after a mutation | Query invalidation |
| Optimistic rollback | A rejected mutation still rolls the cache back correctly | Optimistic updates |
| SSR hydration | Server-fetched data is dehydrated and hydrated with the same key shape | SSR guide |
Two notes from my own work here. First, the React Query Devtools panel is the fastest way to see key shape, freshness, and observer counts — but it is a development tool showing your cache contents, so do not ship it publicly. Second, if you tune defaults globally, prefer an explicit QueryClient over scattered per-hook overrides:
// @tanstack/react-query 5.106.0 — documented v5 API, unchanged by this release
import { QueryClient } from '@tanstack/react-query'
export const queryClient = new QueryClient({
defaultOptions: {
queries: {
staleTime: 30_000,
gcTime: 5 * 60_000,
retry: 1,
refetchOnWindowFocus: false,
},
},
})
export const invoiceKeys = {
all: ['invoices'] as const,
list: (orgId: string) => [...invoiceKeys.all, 'list', { orgId }] as const,
detail: (orgId: string, id: string) => [...invoiceKeys.list(orgId), id] as const,
}
Which Template Capability This Release Supports
A data layer is not a feature you add at the end — it is the layer every screen above it depends on. The buyer question this release informs is concrete: does the template you are evaluating ship a coherent, maintained server-state layer, or a hand-rolled useEffect fetch that every screen reimplements?
Three things separate a real React Query setup from a hand-rolled one, and they are exactly what the release train above is evidence of: the core and the React wrapper are version-locked so behaviour cannot drift between them, the devtools and persister packages move in the same window so your tooling matches your runtime, and the family is published together so a security or bug fix lands atomically.
That is why when I compare SaaS boilerplates, the data layer is one of the rows I check first: a template that pins react-query but ignores query-core alignment, or ships a bespoke fetch hook instead of the library, will cost you more in the first month than it saves at purchase. To see a coherent setup in a finished app, browse the templates and check how the data layer is wired before anything else.
The one caveat worth stating plainly: I am describing what this release is, not what it proves about any template's quality. Version discipline in the upstream library does not automatically mean version discipline in a product built on top of it.
Limitations and Disclosure
Claim types used here. Measured means read directly from npm registry metadata or from diffing the published tarballs. Calculated means arithmetic on those files — the 67-second release window, the file counts. Estimated means my judgment. User-provided means nothing: no metric in this article came from a user, customer, or dashboard.
What I did not do. I did not benchmark 5.106.0 and claim no performance improvement, because the artifacts show there is no code difference to benchmark. I also did not read a changelog — there is none in the registry payload, and the npm description and README do not describe one. If the maintainers shipped a behaviour change without a file diff (a default value change, a network-layer fix), this guide will not show it; check the TanStack Query repository for the source diff and the issue tracker.
Disclosure. I maintain TanStack Ship, and the templates linked above are my own products. I have no material connection to any third party named in this article.
Conclusion and Next Step
TanStack Query 5.106.0 is a low-risk, high-value-to-know release: it is byte-identical to 5.105.3 in the published build, it re-pins the core exactly, and it moves the whole family together — so there is no API work for you to do and one real thing to check, which is that your lockfile is aligned and that you reviewed the 5.105.1 to 5.105.3 range if that is where you are coming from.
Next step: compare SaaS boilerplates and check the data layer row in each one — pinned core and wrapper, coherent devtools, no bespoke fetch hook — then browse the templates and preview the one whose data layer you would not have to rewrite.
FAQ: TanStack Query 5.106.0 Upgrade
Is TanStack Query 5.106.0 a breaking change?
No. It is a minor bump from 5.105.3, and semver requires backwards compatibility. I verified it: zero files differ in the published build/ directory between 5.105.3 and 5.106.0, the only changed file in the package is package.json, the peer range stays react: ^18 || ^19, and the export map is unchanged. Nothing in your code needs to change.
Do I need to upgrade @tanstack/query-core separately?
You do not need to change it by hand — @tanstack/react-query@5.106.0 depends on @tanstack/query-core@5.106.0 with an exact pin, so npm installs the matching core for you. What you should avoid is a stale core left behind by a hand-edited lockfile. Run npm ls @tanstack/query-core after the bump and confirm the tree shows 5.106.0 and nothing older.
Should I move to v6 now?
Not on the basis of 5.106.0. As of the 2026-11-04 publish, npm's latest dist-tag still points at the 5.x line, and that line is still receiving releases. I wrote separately about the v6 network-mode and offline work on this site in August 2026 — read that guide if you are evaluating the migration, but treat it as its own decision.
Is 5.106.0 safe for a production SaaS dashboard?
Nothing in this release makes a dashboard less safe — the code did not change, so the risk profile is identical to 5.105.3, which already includes the 5.105.1 and 5.105.2 changes. The practical risk is procedural: a partial upgrade leaving the core, devtools, and persister on different versions. Align them in one commit, then verify with npm ls.