Skip to content

Conversation

@depfu
Copy link

@depfu depfu bot commented Jan 1, 2026

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ react-router-dom (7.10.1 → 7.11.0) · Repo · Changelog

Release Notes

7.11.0 (from changelog)

Date: 2025-12-17

What's Changed

We've added vite preview support and stabilized the client-side onError API - please make the appropriate changes if you've adopted the unstable_onError API already in a prior release.

vite preview Support

We've added support for vite preview when using Framework mode to make it easy to preview your production build.

Stabilized Client-side onError

The existing <RouterProvider unstable_onError>/<HydratedRouter unstable_onError> APIs have been stabilized as <RouterProvider onError>/<HydratedRouter onError>. Please see the Error Reporting docs for more information.

Call-site Revalidation Opt-out (unstable)

We've added initial unstable support for call-site revalidation opt-out via a new unstable_defaultShouldRevalidate flag (RFC). This flag is available on all navigation/fetcher submission APIs to alter standard revalidation behavior. If any routes include a shouldRevalidate function, then the flag value will be passed to that function so the route has the final say on revalidation behavior.

<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 flag is also available on non-submission navigational use cases - for example, you may want to opt-out of revalidation when adding a search param that doesn't impact the UI:

<Link to="?analytics-param=1" unstable_defaultShouldRevalidate={false} />;
navigate("?analytics-param=1", { unstable_defaultShouldRevalidate: false });
setSearchParams(params, { unstable_defaultShouldRevalidate: false });

Minor Changes

  • react-router - Stabilize <HydratedRouter onError>/<RouterProvider onError> (#14546)
  • @react-router/dev - Add vite preview support (#14507)

Patch Changes

  • react-router - Fix unstable_useTransitions prop on <Router> component to permit omission for backwards compatibility (#14646)
  • react-router - Allow redirects to be returned from client side middleware (#14598)
  • react-router - Handle dataStrategy implementations that return insufficient result sets by adding errors for routes without any available result (#14627)
  • @react-router/serve - Update compression and morgan dependencies to address on-headers CVE: GHSA-76c9-3jph-rj3q (#14652)

Unstable Changes

⚠️ Unstable features are not recommended for production use

  • react-router - RSC: Support for throwing data() and Response from server component render phase (#14632)
    • 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
  • react-router - RSC: Support for throwing redirect Response's at render time (#14596)
  • react-router - RSC: routeRSCServerRequest replace fetchServer with serverResponse (#14597)
  • @react-router/dev - RSC (Framework mode): Manual chunking for react and react-router deps (#14655)
  • @react-router/dev - RSC (Framework mode): Optimize react-server-dom-webpack if in project package.json (#14656)
  • @react-router/{dev,serve} - RSC (Framework mode): Support custom entrypoints (#14643)
  • react-router - Add a new unstable_defaultShouldRevalidate flag to various APIs to allow opt-ing out of standard revalidation behaviors (#14542)

Full Changelog: v7.10.1...v7.11.0

Does any of this look wrong? Please let us know.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot requested a review from canova as a code owner January 1, 2026 15:25
@depfu depfu bot added the dependencies Pull requests that update a dependency file label Jan 1, 2026
@netlify
Copy link

netlify bot commented Jan 1, 2026

Deploy Preview for firefox-devtools-react-contextmenu ready!

Name Link
🔨 Latest commit 3ddef77
🔍 Latest deploy log https://app.netlify.com/projects/firefox-devtools-react-contextmenu/deploys/695691e138e3ef0008941de0
😎 Deploy Preview https://deploy-preview-372--firefox-devtools-react-contextmenu.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant