Version Packages (next) - #594
Merged
Merged
Conversation
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.21
Patch Changes
<endpoint>/data/<id>while rendered action urls stay at the bare<endpoint>/<id>; the router needed no functional change — synthesized form actions already hand the rendered url tocreateServerReference, and the transport re-addresses its own calls — so this updates the wire-shape expectations in tests and the synthesis doc comment. Requires@solidjs/web2.0.0-rc.5 (the release carrying the data-address split); the peer floor is raised to^2.0.0-rc.5.X-Server-Function-Redirect: <status> <resolved-url>(A masked redirect keeps its target in Location on a 200 solid#3102), so the soft/hard split is a real origin comparison — same-origin targets navigate softly withreplace: true(the target takes the submission's place in history, matching HTTP's form-post semantics), anything else hard-navigates — never a guess from how the author spelled the target, which sent relative and absolute spellings down different navigation paths (navigate() from flight-data consumer can silently drop a relative-Location redirect (reliable with absolute URLs) solid#3107). A locally-producedredirect()(a client-side action) still navigates from its real 3xx + Location; aLocationon any other status is the author's data and never navigates.