Skip to content

Conversation

@github-actions
Copy link
Contributor

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

[email protected]

Minor Changes

  • Stabilize <HydratedRouter onError>/<RouterProvider onError> (#14546)

Patch Changes

  • add support for throwing redirect Response's at RSC render time (#14596)

  • Support for throwing data() and Response from server component render phase. Response body is not serialized as async work is not allowed as error encoding phase. If you wish to transmit data to the boundary, throw data() instead. (#14632)

  • Fix unstable_useTransitions prop on <Router> component to permit omission for backewards compatibility (#14646)

  • routeRSCServerRequest replace fetchServer with serverResponse (#14597)

  • [UNSTABLE] Add a new unstable_defaultShouldRevalidate flag to various APIs to allow opt-ing out of standard revalidation behaviors. (#14542)

    If active routes include a shouldRevalidate function, then your value will be passed as defaultShouldRevalidate in those function so that the route always has the final revalidation determination.

    • <Form method="post" unstable_defaultShouldRevalidate={false}>
    • submit(data, { method: "post", unstable_defaultShouldRevalidate: false })
    • <fetcher.Form method="post" unstable_defaultShouldRevalidate={false}>
    • fetcher.submit(data, { method: "post", unstable_defaultShouldRevalidate: false })

    This is also available on non-submission APIs that may trigger revalidations due to changing search params:

    • <Link to="/" unstable_defaultShouldRevalidate={false}>
    • navigate("/?foo=bar", { unstable_defaultShouldRevalidate: false })
    • setSearchParams(params, { unstable_defaultShouldRevalidate: false })
  • Allow redirects to be returned from client side middleware (#14598)

  • Handle dataStrategy implementations that return insufficient result sets by adding errors for routes without any available result (#14627)

@react-router/[email protected]

Minor Changes

  • feat: add vite preview support (#14507)

Patch Changes

  • rsc framework mode manual chunking for react and react-router deps (#14655)
  • add support for throwing redirect Response's at RSC render time (#14596)
  • support custom entrypoints for RSC framework mode (#14643)
  • routeRSCServerRequest replace fetchServer with serverResponse (#14597)
  • rsc framewlrk mode - optimize react-server-dom-webpack if in project package.json (#14656)
  • Updated dependencies:

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

[email protected]

@brophdawg11 brophdawg11 merged commit b34a9cd into release-next Dec 17, 2025
10 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch December 17, 2025 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants