Version Packages #8118
Merged
Version Packages #8118
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
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 upcoming, this PR will be updated.
Releases
@builder.io/qwik-city@1.17.2
Patch Changes
🐞🩹 history behavior in some edge cases has been brought inline with the E2E tests that were accidentally disabled. (the tests can't be disabled any more either) (by @wmertens in
206f3e0)🐞🩹 SPA routing is broken unless origin matches value in in vite.config [🐞] [v1 & v2] SPA routing is broken unless origin matches value in in vite.config #8093 (by @termermc in #8097)
If the SSG origin was set to
localhost:3000and a user visited from127.0.0.1:3000, SPA routing would be broken.Internally, useNavigate's context provider
gotochecks the new destination with the last route location. If theorigin is different, it just does a normal browser navigation. This makes sense; links to other origins cannot use
SPA routing. However, the initial route it compares was using an origin that came from the server environment.
Now, the first navigation will set that initial route to the browser's actual href, eliminating the erroneous
origin mismatch for SPA navigations.
🐞🩹
thisin various Qwik-City handlers is nowRequestEventagain. (by @wmertens in #8111)create-qwik@1.17.2
eslint-plugin-qwik@1.17.2
@builder.io/qwik@1.17.2