chore: Update version for release (pre) #10499
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
github-actions
bot
force-pushed
the
changeset-release/release-next
branch
from
74de627 to
2f93187
Compare
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 release-next, this PR will be updated.
release-nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonrelease-next.Releases
@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
When using Lazy Route Disscovery (
future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)fetchercalls to undiscovered routes, this mismatch will trigger a document reload of the current path<Link>components, mismatches will result in a no-opUpdated dependencies:
@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]@remix-run/[email protected]
Patch Changes
When using Lazy Route Disscovery (
future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)fetchercalls to undiscovered routes, this mismatch will trigger a document reload of the current path<Link>components, mismatches will result in a no-op@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected][email protected]
[email protected]
remixSee the
CHANGELOG.mdin individual Remix packages for all changes.@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]