From dc2688dca71f800fc0e66dc02a41b5bc2ed3bf22 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 30 Sep 2026 21:00:52 +0000 Subject: [PATCH] Version Packages (next) --- .changeset/pre.json | 1 + CHANGELOG.md | 6 ++++++ package.json | 2 +- 3 files changed, 8 insertions(+), 1 deletion(-) diff --git a/.changeset/pre.json b/.changeset/pre.json index a25ec729..98024eff 100644 --- a/.changeset/pre.json +++ b/.changeset/pre.json @@ -56,6 +56,7 @@ "public-hydration-api", "query-cache-prototype-keys", "query-decodes-redirect-carrier", + "query-hydration-hang", "query-implies-get", "query-prototype-keys", "query-redirect-revalidate-pending", diff --git a/CHANGELOG.md b/CHANGELOG.md index ef3c9de7..0956022a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,11 @@ # @solidjs/router +## 2.0.0-next.33 + +### Patch Changes + +- d8288bd: Fix navigations hanging after hydration when a `query()` read ran inside Solid's hydration tracking run, where the global `Promise` and `fetch` are swapped for stubs that never settle (solidjs/solid#3721). Adopting a server value that had already settled wrapped it with that stubbed `Promise`, so the cache kept a promise that never settled. A boundary resuming more than 5s after boot treated the entry adopted at boot as stale and called the query function inside the tracking run, caching the same kind of promise. Adopted values are now wrapped with the native `Promise`, and a read with no navigation in flight while hydrating reuses the cached entry at any age, as adoption already did for server payloads. Navigations keep the normal freshness windows. + ## 2.0.0-next.32 ### Patch Changes diff --git a/package.json b/package.json index 49f3f0e3..068b6d1e 100644 --- a/package.json +++ b/package.json @@ -6,7 +6,7 @@ "Ryan Turnquist" ], "license": "MIT", - "version": "2.0.0-next.32", + "version": "2.0.0-next.33", "homepage": "https://github.com/solidjs/solid-router#readme", "repository": { "type": "git",