Version Packages (next) - #645
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
September 30, 2026 21:00
3c6716e to
dc2688d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
@solidjs/router@2.0.0-next.33
Patch Changes
query()read ran inside Solid's hydration tracking run, where the globalPromiseandfetchare swapped for stubs that never settle (Navigation during streaming hydration never settles its transition; later navigations silently dropped solid#3721). Adopting a server value that had already settled wrapped it with that stubbedPromise, 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 nativePromise, 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.