chore: Update version for release #10204
Merged
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.
Releases
@remix-run/[email protected]
Minor Changes
Add support for
routes.ts
behindfuture.unstable_routeConfig
flag to assist with the migration to React Router v7. (#10107)Config-based routing is the new default in React Router v7, configured via the
routes.ts
file in the app directory. Support forroutes.ts
and its related APIs in Remix are designed as a migration path to help minimize the number of changes required when moving your Remix project over to React Router v7. While some new packages have been introduced within the@remix-run
scope, these new packages only exist to keep the code inroutes.ts
as similar as possible to the equivalent code for React Router v7.When the
unstable_routeConfig
future flag is enabled, Remix's built-in file system routing will be disabled and your project will opted into React Router v7's config-based routing.To enable the flag, in your
vite.config.ts
file:A minimal
routes.ts
file to support Remix's built-in file system routing looks like this:@deprecated
annotations tojson
/defer
utilitiesPatch Changes
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
@remix-run/eslint-config
(#10174)@remix-run/[email protected]
Minor Changes
SerializeFrom
in favor of generics because it will be removed in React Router v7 (#10173)Patch Changes
@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]
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Patch Changes
18e9d69d1
)defaultShouldRevalidate
value when using single fetch (#10139)@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]
[email protected]
[email protected]
remix
See the
CHANGELOG.md
in individual Remix packages for all changes.@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]