chore: Update version for release (pre) #13014
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.
release-next
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onrelease-next
.Releases
react-router@7.2.0-pre.1
Minor Changes
New type-safe
href
utility that guarantees links point to actual paths in your app (#13012)Patch Changes
Fix typegen for repeated params (#13012)
In React Router, path parameters are keyed by their name.
So for a path pattern like
/a/:id/b/:id?/c/:id
, the last:id
will set the value forid
inuseParams
and theparams
prop.For example,
/a/1/b/2/c/3
will result in the value{ id: 3 }
at runtime.Previously, generated types for params incorrectly modeled repeated params with an array.
So
/a/1/b/2/c/3
generated a type like{ id: [1,2,3] }
.To be consistent with runtime behavior, the generated types now correctly model the "last one wins" semantics of path parameters.
So
/a/1/b/2/c/3
now generates a type like{ id: 3 }
.@react-router/dev@7.2.0-pre.1
Minor Changes
New type-safe
href
utility that guarantees links point to actual paths in your app (#13012)Patch Changes
Fix typegen for repeated params (#13012)
In React Router, path parameters are keyed by their name.
So for a path pattern like
/a/:id/b/:id?/c/:id
, the last:id
will set the value forid
inuseParams
and theparams
prop.For example,
/a/1/b/2/c/3
will result in the value{ id: 3 }
at runtime.Previously, generated types for params incorrectly modeled repeated params with an array.
So
/a/1/b/2/c/3
generated a type like{ id: [1,2,3] }
.To be consistent with runtime behavior, the generated types now correctly model the "last one wins" semantics of path parameters.
So
/a/1/b/2/c/3
now generates a type like{ id: 3 }
.Fix
ArgError: unknown or unexpected option: --version
when runningreact-router --version
(#13012)Updated dependencies:
react-router@7.2.0-pre.1
@react-router/node@7.2.0-pre.1
@react-router/serve@7.2.0-pre.1
@react-router/architect@7.2.0-pre.1
Patch Changes
react-router@7.2.0-pre.1
@react-router/node@7.2.0-pre.1
@react-router/cloudflare@7.2.0-pre.1
Patch Changes
react-router@7.2.0-pre.1
react-router-dom@7.2.0-pre.1
Patch Changes
react-router@7.2.0-pre.1
@react-router/express@7.2.0-pre.1
Patch Changes
react-router@7.2.0-pre.1
@react-router/node@7.2.0-pre.1
@react-router/fs-routes@7.2.0-pre.1
Patch Changes
@react-router/dev@7.2.0-pre.1
@react-router/node@7.2.0-pre.1
Patch Changes
react-router@7.2.0-pre.1
@react-router/remix-routes-option-adapter@7.2.0-pre.1
Patch Changes
@react-router/dev@7.2.0-pre.1
@react-router/serve@7.2.0-pre.1
Patch Changes
react-router@7.2.0-pre.1
@react-router/node@7.2.0-pre.1
@react-router/express@7.2.0-pre.1
create-react-router@7.2.0-pre.1