[pull] main from remix-run:main

CHANGELOG.md

@@ -13,6 +13,7 @@ We manage release notes in this file instead of the paginated Github Releases Pa
   <summary>Table of Contents</summary>
 
 - [React Router Releases](#react-router-releases)
+  - [v7.15.0](#v7150)
   - [v7.14.2](#v7142)
   - [v7.14.1](#v7141)
   - [v7.14.0](#v7140)
@@ -169,6 +170,76 @@ We manage release notes in this file instead of the paginated Github Releases Pa
 
 </details>
 
+## v7.15.0
+
+Date: 2026-05-05
+
+### What's Changed
+
+#### Stabilizations
+
+We've stabilized a bunch of APIs in this release in preparation for a React Router v8 release hopefully in the next month or two. These flag/prop renames are breaking changes if you've already opted into the unstable APIs so please make sure you make the appropriate changes if so.
+
+- `future.unstable_passThroughRequests` → `future.v8_passThroughRequests`
+- `future.unstable_subResourceIntegrity` → top-level `config.subResourceIntegrity`
+- `prerender.unstable_concurrency` → `prerender.concurrency`
+- `unstable_url` → `url` (loader, action, middleware, instrumentation args)
+- `unstable_instrumentations` → `instrumentations`
+  - Plus associated types (`ServerInstrumentation`, `ClientInstrumentation`, etc.)
+- `unstable_pattern` → `pattern` (loader, action, middleware, instrumentation args)
+- `unstable_defaultShouldRevalidate` → `defaultShouldRevalidate`
+- `unstable_useTransitions` → `useTransitions`
+- `unstable_mask` → `mask` (on `<Link>`, `useLinkClickHandler`, `useNavigate`, and `Location`)
+
+#### Route matching optimizations
+
+We've added a handful of route matching optimizations in this release for Framework and Data mode. The changes are mostly related to caching the internal flattened/ranked route branches and reducing additional calls to `matchRoutes` along the critical path. This should result in improved performance during both server-side request handling and client-side navigations.
+
+### Minor Changes
+
+- `react-router` - Stabilize `unstable_defaultShouldRevalidate` as `defaultShouldRevalidate` on `<Link>`, `<Form>`, `useLinkClickHandler`, `useSubmit`, `fetcher.submit`, and `setSearchParams` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `react-router` - Stabilize the instrumentation APIs ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - `unstable_instrumentations` is now `instrumentations`
+  - `unstable_pattern` is now `pattern`
+  - The `unstable_ServerInstrumentation`, `unstable_ClientInstrumentation`, `unstable_InstrumentRequestHandlerFunction`, `unstable_InstrumentRouterFunction`, `unstable_InstrumentRouteFunction`, and `unstable_InstrumentationHandlerResult` types have had their `unstable_` prefixes removed
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `react-router` - Stabilize `unstable_mask` as `mask` on `<Link>`, `useLinkClickHandler`, and `useNavigate`, and rename the corresponding `Location.unstable_mask` field to `Location.mask` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `react-router` - Stabilize the `unstable_normalizePath` option on `staticHandler.query` and `staticHandler.queryRoute` as `normalizePath` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `react-router` - Stabilize `future.unstable_passThroughRequests` as `future.v8_passThroughRequests` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `react-router` - Remove `unstable_subResourceIntegrity` from the runtime `FutureConfig` type; the flag is now controlled by the top-level `subResourceIntegrity` option in `react-router.config.ts` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `react-router` - Stabilize `unstable_url` as `url` on `loader`, `action`, and `middleware` function args ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `react-router` - Stabilize `unstable_useTransitions` as `useTransitions` on `<BrowserRouter>`, `<HashRouter>`, `<HistoryRouter>`, `<MemoryRouter>`, `<Router>`, `<RouterProvider>`, `<HydratedRouter>`, and `useLinkClickHandler` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `@react-router/dev` - Stabilize `future.unstable_passThroughRequests` as `future.v8_passThroughRequests` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `@react-router/dev` - Stabilize `prerender.unstable_concurrency` as `prerender.concurrency` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+- `@react-router/dev` - Stabilize `future.unstable_subResourceIntegrity` as a top-level `subResourceIntegrity` config option in `react-router.config.ts` ([14999](https://github.com/remix-run/react-router/pull/14999))
+  - ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
+
+### Patch Changes
+
+- `react-router` - Add `nonce` to `<Scripts>` `<link rel="modulepreload">` elements (if provided) ([af5d49b](https://github.com/remix-run/react-router/commit/af5d49b))
+- `react-router` - Fix a bug with `unstable_defaultShouldRevalidate={false}` where parent routes that did not export a `shouldRevalidate` function could be incorrectly included in the single fetch call for new child route data ([#15012](https://github.com/remix-run/react-router/pull/15012))
+- `react-router` - Mark `mask` as an optional field in `Location` for easier mocking in unit tests ([#14999](https://github.com/remix-run/react-router/pull/14999))
+- `react-router` - Improve server-side route matching performance by pre-computing flattened/cached route branches ([#14967](https://github.com/remix-run/react-router/pull/14967)) ([af5d49b](https://github.com/remix-run/react-router/commit/af5d49b))
+  - Performance benchmarks showed roughly a 10-15% improvement in server-side request handling performance
+- `react-router` - Cache flattened/ranked route branches to optimize server-side route matching ([#14967](https://github.com/remix-run/react-router/pull/14967))
+- `react-router` - Improve route matching performance in Framework/Data Mode ([#14971](https://github.com/remix-run/react-router/pull/14971)) ([af5d49b](https://github.com/remix-run/react-router/commit/af5d49b))
+  - Avoiding unnecessary calls to `matchRoutes` in data router scenarios
+    - This includes adding back the optimization that was removed in `7.6.0` ([#13562](https://github.com/remix-run/react-router/pull/13562))
+    - The issues that prompted the revert have been addressed by using the available router `matches` but always updating `match.route` to the latest route in the `manifest`
+  - Leverage pre-computed pre-computing flattened/cached route branches during client side route matching
+  - Performance benchmarks showed roughly a 15-30% improvement in server-side request handling performance
+
+**Full Changelog**: [`v7.14.2...v7.15.0`](https://github.com/remix-run/react-router/compare/react-router@7.14.2...react-router@7.15.0)
+
 ## v7.14.2
 
 Date: 2026-04-21

contributors.yml

@@ -3,6 +3,7 @@
 - 43081j
 - aarbi
 - abdallah-nour
+- abdulwahaab710
 - abeadam
 - abhi-kr-2100
 - abhijeetpandit7
@@ -349,6 +350,7 @@
 - pwdcd
 - pyitphyoaung
 - qu0b
+- Quatton
 - QzCurious
 - raphaelbronsveld
 - redabacha

decisions/0015-observability.md

@@ -234,7 +234,7 @@ let unInstrumentedHandler = createRequestHandler({
         ...m.entry,
         module: {
           ...m.entry.module,
-          unstable_instrumentations: undefined,
+          instrumentations: undefined,
         },
       },
     })),

docs/api/components/Form.md

@@ -144,7 +144,7 @@ Enables a [View Transition](https://developer.mozilla.org/en-US/docs/Web/API/Vie
 for this navigation. To apply specific styles during the transition, see
 [`useViewTransitionState`](../hooks/useViewTransitionState).
 
-### unstable_defaultShouldRevalidate
+### defaultShouldRevalidate
 
 Specify the default revalidation behavior after this submission
 

docs/api/components/Link.md

@@ -214,14 +214,14 @@ for this navigation.
 
 To apply specific styles for the transition, see [`useViewTransitionState`](../hooks/useViewTransitionState)
 
-### unstable_defaultShouldRevalidate
+### defaultShouldRevalidate
 
 [modes: framework, data, declarative]
 
 Specify the default revalidation behavior for the navigation.
 
 ```tsx
-<Link to="/some/path" unstable_defaultShouldRevalidate={false} />
+<Link to="/some/path" defaultShouldRevalidate={false} />
 ```
 
 If no `shouldRevalidate` functions are present on the active routes, then this
@@ -232,7 +232,7 @@ useful when updating search params and you don't want to trigger a revalidation.
 By default (when not specified), loaders will revalidate according to the routers
 standard revalidation behavior.
 
-### unstable_mask
+### mask
 
 [modes: framework, data]
 
@@ -265,7 +265,7 @@ export default function Gallery({ loaderData }: Route.ComponentProps) {
          <Link
            key={image.id}
            to={`/gallery?image=${image.id}`}
-           unstable_mask={`/images/${image.id}`}
+           mask={`/images/${image.id}`}
          >
            <img src={image.url} alt={image.alt} />
          </Link>

docs/api/data-routers/RouterProvider.md

@@ -49,7 +49,7 @@ function RouterProvider({
   router,
   flushSync: reactDomFlushSyncImpl,
   onError,
-  unstable_useTransitions,
+  useTransitions,
 }: RouterProviderProps): React.ReactElement
 ```
 
@@ -78,7 +78,7 @@ and is only present for render errors.
 
 ```tsx
 <RouterProvider onError=(error, info) => {
-  let { location, params, unstable_pattern, errorInfo } = info;
+  let { location, params, pattern, errorInfo } = info;
   console.error(error, location, errorInfo);
   reportToErrorService(error, location, errorInfo);
 }} />
@@ -88,7 +88,7 @@ and is only present for render errors.
 
 The [`DataRouter`](https://api.reactrouter.com/v7/interfaces/react-router.DataRouter.html) instance to use for navigation and data fetching.
 
-### unstable_useTransitions
+### useTransitions
 
 Control whether router state updates are internally wrapped in
 [`React.startTransition`](https://react.dev/reference/react/startTransition).
@@ -105,5 +105,5 @@ Control whether router state updates are internally wrapped in
 - When set to `false`, the router will not leverage `React.startTransition` or
   `React.useOptimistic` on any navigations or state changes.
 
-For more information, please see the [docs](https://reactrouter.com/explanation/react-transitions).
+For more information, please see the [docs](../../explanation/react-transitions).
 

docs/api/data-routers/createBrowserRouter.md

@@ -172,7 +172,7 @@ const router = createBrowserRouter(
 );
 ```
 
-### opts.unstable_instrumentations
+### opts.instrumentations
 
 Array of instrumentation objects allowing you to instrument the router and
 individual routes prior to router initialization (and on any subsequently
@@ -183,7 +183,7 @@ tracing.  See the [docs](../../how-to/instrumentation) for more information.
 
 ```tsx
 let router = createBrowserRouter(routes, {
-  unstable_instrumentations: [logging]
+  instrumentations: [logging]
 });
 
 

docs/api/data-routers/createHashRouter.md

@@ -142,7 +142,7 @@ const router = createBrowserRouter(
 );
 ```
 
-### opts.unstable_instrumentations
+### opts.instrumentations
 
 Array of instrumentation objects allowing you to instrument the router and
 individual routes prior to router initialization (and on any subsequently
@@ -153,7 +153,7 @@ tracing.  See the [docs](../../how-to/instrumentation) for more information.
 
 ```tsx
 let router = createBrowserRouter(routes, {
-  unstable_instrumentations: [logging]
+  instrumentations: [logging]
 });
 
 

docs/api/data-routers/createMemoryRouter.md

@@ -99,7 +99,7 @@ Initial entries in the in-memory history stack
 
 Index of `initialEntries` the application should initialize to
 
-### opts.unstable_instrumentations
+### opts.instrumentations
 
 Array of instrumentation objects allowing you to instrument the router and
 individual routes prior to router initialization (and on any subsequently
@@ -110,7 +110,7 @@ tracing.  See the [docs](../../how-to/instrumentation) for more information.
 
 ```tsx
 let router = createBrowserRouter(routes, {
-  unstable_instrumentations: [logging]
+  instrumentations: [logging]
 });
 
 

docs/api/data-routers/createStaticRouter.md

@@ -48,6 +48,7 @@ function createStaticRouter(
   routes: RouteObject[],
   context: StaticHandlerContext,
   opts: {
+    branches?: RouteBranch<DataRouteObject>[];
     future?: Partial<FutureConfig>;
   } = ,
 ): DataRouter {}
@@ -67,6 +68,10 @@ The [`StaticHandlerContext`](https://api.reactrouter.com/v7/interfaces/react-rou
 
 Future flags for the static [`DataRouter`](https://api.reactrouter.com/v7/interfaces/react-router.DataRouter.html)
 
+### opts.branches
+
+Optional pre-computed route branches
+
 ## Returns
 
 A static [`DataRouter`](https://api.reactrouter.com/v7/interfaces/react-router.DataRouter.html) that can be used to render the provided routes

docs/api/declarative-routers/BrowserRouter.md

@@ -31,7 +31,7 @@ API for client-side routing.
 function BrowserRouter({
   basename,
   children,
-  unstable_useTransitions,
+  useTransitions,
   window,
 }: BrowserRouterProps)
 ```
@@ -46,7 +46,7 @@ Application basename
 
 ``<Route>`` components describing your route configuration
 
-### unstable_useTransitions
+### useTransitions
 
 Control whether router state updates are internally wrapped in
 [`React.startTransition`](https://react.dev/reference/react/startTransition).
@@ -59,7 +59,7 @@ Control whether router state updates are internally wrapped in
 - When set to `false`, the router will not leverage `React.startTransition`
   on any navigations or state changes.
 
-For more information, please see the [docs](https://reactrouter.com/explanation/react-transitions).
+For more information, please see the [docs](../../explanation/react-transitions).
 
 ### window
 

docs/api/declarative-routers/HashRouter.md

@@ -32,7 +32,7 @@ of the URL so it is not sent to the server.
 function HashRouter({
   basename,
   children,
-  unstable_useTransitions,
+  useTransitions,
   window,
 }: HashRouterProps)
 ```
@@ -47,7 +47,7 @@ Application basename
 
 ``<Route>`` components describing your route configuration
 
-### unstable_useTransitions
+### useTransitions
 
 Control whether router state updates are internally wrapped in
 [`React.startTransition`](https://react.dev/reference/react/startTransition).
@@ -60,7 +60,7 @@ Control whether router state updates are internally wrapped in
 - When set to `false`, the router will not leverage `React.startTransition`
   on any navigations or state changes.
 
-For more information, please see the [docs](https://reactrouter.com/explanation/react-transitions).
+For more information, please see the [docs](../../explanation/react-transitions).
 
 ### window
 

docs/api/declarative-routers/HistoryRouter.md

@@ -43,7 +43,7 @@ function HistoryRouter({
   basename,
   children,
   history,
-  unstable_useTransitions,
+  useTransitions,
 }: HistoryRouterProps)
 ```
 
@@ -61,7 +61,7 @@ Application basename
 
 A `History` implementation for use by the router
 
-### unstable_useTransitions
+### useTransitions
 
 Control whether router state updates are internally wrapped in
 [`React.startTransition`](https://react.dev/reference/react/startTransition).
@@ -74,5 +74,5 @@ Control whether router state updates are internally wrapped in
 - When set to `false`, the router will not leverage `React.startTransition`
   on any navigations or state changes.
 
-For more information, please see the [docs](https://reactrouter.com/explanation/react-transitions).
+For more information, please see the [docs](../../explanation/react-transitions).
 

docs/api/declarative-routers/MemoryRouter.md

@@ -32,7 +32,7 @@ function MemoryRouter({
   children,
   initialEntries,
   initialIndex,
-  unstable_useTransitions,
+  useTransitions,
 }: MemoryRouterProps): React.ReactElement
 ```
 
@@ -54,7 +54,7 @@ Initial entries in the in-memory history stack
 
 Index of `initialEntries` the application should initialize to
 
-### unstable_useTransitions
+### useTransitions
 
 Control whether router state updates are internally wrapped in
 [`React.startTransition`](https://react.dev/reference/react/startTransition).
@@ -67,5 +67,5 @@ Control whether router state updates are internally wrapped in
 - When set to `false`, the router will not leverage `React.startTransition`
   on any navigations or state changes.
 
-For more information, please see the [docs](https://reactrouter.com/explanation/react-transitions).
+For more information, please see the [docs](../../explanation/react-transitions).
 

docs/api/declarative-routers/Router.md

@@ -38,7 +38,7 @@ function Router({
   navigationType = NavigationType.Pop,
   navigator,
   static: staticProp = false,
-  unstable_useTransitions,
+  useTransitions,
 }: RouterProps): React.ReactElement | null
 ```
 
@@ -72,7 +72,7 @@ or a custom navigator that implements the [`Navigator`](https://api.reactrouter.
 Whether this router is static or not (used for SSR). If `true`, the router
 will not be reactive to location changes.
 
-### unstable_useTransitions
+### useTransitions
 
 Control whether router state updates are internally wrapped in
 [`React.startTransition`](https://react.dev/reference/react/startTransition).
@@ -85,5 +85,5 @@ Control whether router state updates are internally wrapped in
 - When set to `false`, the router will not leverage `React.startTransition`
   on any navigations or state changes.
 
-For more information, please see the [docs](https://reactrouter.com/explanation/react-transitions).
+For more information, please see the [docs](../../explanation/react-transitions).