Version Packages (next) - #642
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
4 times, most recently
from
September 30, 2026 07:51
3236635 to
0c326ef
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
September 30, 2026 07:55
0c326ef to
78768dd
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
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.32
Patch Changes
1db62b1: Observe tier: the router declares the route the document arrived on, with the same
OBSERVE.attribution.withOrigincall it makes for every navigation — around the work that builds its context (initial: trueon the ref), on both sides. On the client this is the first"navigation"record (initial: true,atthe document's navigation start, no write to wait for); on the server the same declaration names the request's"render"record (RenderEvent.route: the matched pattern, the path, the params). A consumer naming page loads and requests by route (/users/:idrather than one name per user) had this for every navigation but the first; now it has the first too. Nothing in production builds:OBSERVEis undefined there and the declaration folds out. Needssolid-js/@solidjs/web2.0.0-rc.12or later (NavigationRef.initial,RenderEvent.route), already inside the^2.0.0-rc.13peer range.2b2f244: Move off
sharedConfigonto Solid's public hydration APIs:query()writes server results withgetHydrationWriter()(gated byisHydratable(), so<NoHydration>suppresses it) and adopts them on the client withtakeHydrationValue(). Drops the obsoletesharedConfig.donewrite on the first location change. Requires solid-js / @solidjs/web 2.0.0-rc.13; peer range now^2.0.0-rc.13.daa7713: Include own
__proto__properties when generating query cache keys. Arguments that differ in those values now use separate cache entries instead of returning another argument's cached result.4b5cb10: Parse search parameters such as
constructor,toStringand__proto__as ordinary keys. Single values remain strings, repeated values keep URL order, and all parsed keys are included in enumeration and serialization.6e47fbb: Keep
location.querydata stable when navigation changes only the pathname or hash. Consumers that enumerate the query no longer rerun when the search string is unchanged, and repeated parameters keep the same array references.87b5caa: Keep query responses from changing an SSR page's content type or making it download as a file. Representation metadata such as
Content-Language,ETagandLast-Modifiedalso stays on the query response. UsehttpHeader()from@solidjs/webto set these headers on the page itself.Append cookies once per cached query result. New results can still update cookies, and redirects continue to work after streaming starts.