Repository navigation
Version Packages (next) - #686
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
October 20, 2026 17:57
8139172 to
42462de
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.41
Patch Changes
actiontoformAction(and theActiontype toFormAction): it is the form layer — submissions,aria-busy, no-JS posts,.with()— whileactionis solid-js's own primitive.actionandActionstay as deprecated aliases with a dev warning until the next major.useActionis deprecated with no replacement: call the server function (or a coreaction) directly, since the router now applies revalidation and redirects on any server function call.singleFlight={false}), so a server function called straight from an event handler gets itsX-Revalidatekeys, redirect and flight data applied without an action. Query reads, the flight consumer and actions now share one redirect/revalidation path, so action redirects resolve against the router base the same way query redirects do.query()stamps the fetch it starts, and every wrapper it hands a reader, with when that fetch started (OBSERVE.attribution.markFlight, observe and dev builds only). Page data a route's preload started, and read a render pass later behind the page's lazy chunk, no longer reads as a waterfall toASYNC_WATERFALLorSSR_BOUNDARY_WATERFALL. Takes effect with the solid release that carries the stamps on its core slot (fix(solid): judge SSR waterfall waits by when their work started solid#4108); older versions ignore it.