fix(deps): update react-router monorepo to v7 (major) by renovate[bot] · Pull Request #875 · logto-io/js

renovate · 2024-12-05T05:13:19Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
react-router-dom (source)	`^6.2.2` → `^7.0.0`
react-router@>=6.0.0 <6.30.2 (source)	[`^6.30.2` → `^7.0.0`](https://renovatebot.com/diffs/npm/react-router@>=6.0.0 <6.30.2/6.30.3/7.14.0)

Release Notes

remix-run/react-router (react-router-dom)

`v7.14.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.14.0

`v7.13.2`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.13.2

`v7.13.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.13.1

`v7.13.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.13.0

`v7.12.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.12.0

`v7.11.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.11.0

`v7.10.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.10.1

`v7.10.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.10.0

`v7.9.6`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.6

`v7.9.5`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.5

`v7.9.4`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.4

`v7.9.3`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.3

`v7.9.2`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.2

`v7.9.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.1

`v7.9.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.0

`v7.8.2`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.8.2

`v7.8.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.8.1

`v7.8.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.8.0

`v7.7.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.7.1

`v7.7.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.7.0

`v7.6.3`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.6.3

`v7.6.2`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.6.2

`v7.6.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.6.1

`v7.6.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.6.0

`v7.5.3`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.5.3

`v7.5.2`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.5.2

`v7.5.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.5.1

`v7.5.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.5.0

`v7.4.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.4.1

`v7.4.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.4.0

`v7.3.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.3.0

`v7.2.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.2.0

`v7.1.5`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.1.5

`v7.1.4`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.1.4

`v7.1.3`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.1.3

`v7.1.2`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.1.2

`v7.1.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.1.1

`v7.1.0`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.1.0

`v7.0.2`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.0.2

`v7.0.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.0.1

`v7.0.0`

Compare Source

Major Changes

Remove the original defer implementation in favor of using raw promises via single fetch and turbo-stream. This removes these exports from React Router: (#11744)
- defer
- AbortedDeferredError
- type TypedDeferredData
- UNSAFE_DeferredData
- UNSAFE_DEFERRED_SYMBOL,
Use createRemixRouter/RouterProvider in entry.client instead of RemixBrowser (#11469)
Remove single fetch future flag. (#11522)
Remove future.v7_startTransition flag (#11696)
Remove future.v7_normalizeFormMethod future flag (#11697)
Allow returning undefined from actions and loaders (#11680)
update minimum node version to 18 (#11690)
Remove future.v7_prependBasename from the ionternalized @remix-run/router package (#11726)
Remove future.v7_throwAbortReason from internalized @remix-run/router package (#11728)
Add exports field to all packages (#11675)
node package no longer re-exports from react-router (#11702)
updates the minimum React version to 18 (#11689)
- Remove the future.v7_partialHydration flag (#11725)
  - This also removes the <RouterProvider fallbackElement> prop
    - To migrate, move the fallbackElement to a hydrateFallbackElement/HydrateFallback on your root route
  - Also worth nothing there is a related breaking changer with this future flag:
    - Without future.v7_partialHydration (when using fallbackElement), state.navigation was populated during the initial load
    - With future.v7_partialHydration, state.navigation remains in an "idle" state during the initial load
Remove future.v7_fetcherPersist flag (#11731)

Minor Changes

Add prefetching support to Link/NavLink when using Remix SSR (#11402)
Enhance ScrollRestoration so it can restore properly on an SSR'd document load (#11401)
Add built-in Remix-style hydration support to RouterProvider. When running from a Remix-SSR'd HTML payload with the proper window variables (__remixContext, __remixManifest, __remixRouteModules), you don't need to pass a router prop and RouterProvider will create the router for you internally. (#11396) (#11400)

Patch Changes

Memoize some RouterProvider internals to reduce uneccesary re-renders (#11817)
Updated dependencies:
- react-router@7.0.0

What's Changed

Throw an error if an action/loader function returns undefined as revalidations need to know whether the loader has previously been executed. undefined also causes issues during SSR stringification for hydration. You should always ensure your loader/action returns a value, and you may return null if you don't wish to return anything. (#9511)
Properly handle redirects to external domains (#9590, #9654)
Preserve the HTTP method on 307/308 redirects (#9597)
Support basename in static data routers (#9591)
Enhanced ErrorResponse bodies to contain more descriptive text in internal 403/404/405 scenarios
Fix issues with encoded characters in NavLink and descendant <Routes> (#9589, #9647)
Properly serialize/deserialize ErrorResponse instances when using built-in hydration (#9593)
Support basename in static data routers (#9591)
Updated dependencies:
- @remix-run/router@1.0.4
- react-router@6.4.4

Full Changelog: https://github.com/remix-run/react-router/compare/react-router-dom@6.4.3...react-router-dom@6.4.4

`v6.4.3`

Compare Source

`v6.4.2`

Compare Source

`v6.4.1`

Compare Source

`v6.4.0`

Compare Source

`v6.3.0`: react-router@v6.3.0

Compare Source

What's Changed

Added the v5 to v6 backwards compatibility package 💜 (#8752). The official guide can be found in this discussion

New Contributors

@mfijas made their first contribution in #8717
@ThornWu made their first contribution in #8718
@janpaepke made their first contribution in #8651
@rtmann made their first contribution in #8725

Full Changelog: remix-run/react-router@v6.2.2...v6.3.0

remix-run/react-router (react-router@>=6.0.0 <6.30.2)

`v7.14.0`

Compare Source

Patch Changes

UNSTABLE RSC FRAMEWORK MODE BREAKING CHANGE - Existing route module exports remain unchanged from stable v7 non-RSC mode, but new exports are added for RSC mode. If you want to use RSC features, you will need to update your route modules to export the new annotations. (#14901)

If you are using RSC framework mode currently, you will need to update your route modules to the new conventions. The following route module components have their own mutually exclusive server component counterparts:

Server Component Export Client Component

ServerComponent default

ServerErrorBoundary ErrorBoundary

ServerLayout Layout

ServerHydrateFallback HydrateFallback

If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also server components. If you want to keep those as server components, you can rename them and prefix them with Server. If you were previously importing the implementations of those components from a client module, you can simply inline them.

Example:

Before
```
import { ErrorBoundary as ClientErrorBoundary } from "./client";

export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  return <ClientErrorBoundary />;
}

export function Layout() {
  // ...
}

export function HydrateFallback() {
  // ...
}
```
After
```
export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  // previous implementation of ClientErrorBoundary, this is now a client component
}

export function ServerLayout() {
  // rename previous Layout export to ServerLayout to make it a server component
}

export function ServerHydrateFallback() {
  // rename previous HydrateFallback export to ServerHydrateFallback to make it a server component
}
```
rsc Link prefetch (#14902)
Remove recursion from turbo-stream v2 allowing for encoding / decoding of massive payloads. (#14838)
encodeViaTurboStream leaked memory via unremoved AbortSignal listener (#14900)

`v7.13.2`

Compare Source

Patch Changes

Fix clientLoader.hydrate when an ancestor route is also hydrating a clientLoader (#14835)
Fix type error when passing Framework Mode route components using Route.ComponentProps to createRoutesStub (#14892)
Fix percent encoding in relative path navigation (#14786)

Add future.unstable_passThroughRequests flag (#14775)

By default, React Router normalizes the request.url passed to your loader, action, and middleware functions by removing React Router's internal implementation details (.data suffixes, index + _routes query params).

Enabling this flag removes that normalization and passes the raw HTTP request instance to your handlers. This provides a few benefits:

Reduces server-side overhead by eliminating multiple new Request() calls on the critical path
Allows you to distinguish document from data requests in your handlers base don the presence of a .data suffix (useful for observability purposes)

If you were previously relying on the normalization of request.url, you can switch to use the new sibling unstable_url parameter which contains a URL instance representing the normalized location:

// ❌ Before: you could assume there was no `.data` suffix in `request.url`
export async function loader({ request }: Route.LoaderArgs) {
  let url = new URL(request.url);
  if (url.pathname === "/path") {
    // This check will fail with the flag enabled because the `.data` suffix will
    // exist on data requests
  }
}

// ✅ After: use `unstable_url` for normalized routing logic and `request.url`
// for raw routing logic
export async function loader({ request, unstable_url }: Route.LoaderArgs) {
  if (unstable_url.pathname === "/path") {
    // This will always have the `.data` suffix stripped
  }

  // And now you can distinguish between document versus data requests
  let isDataRequest = new URL(request.url).pathname.endsWith(".data");
}

Internal refactor to consolidate framework-agnostic/React-specific route type layers - no public API changes (#14765)
Sync protocol validation to rsc flows (#14882)
Add a new unstable_url: URL parameter to route handler methods (loader, action, middleware, etc.) representing the normalized URL the application is navigating to or fetching, with React Router implementation details removed (.datasuffix, index/_routes query params) (#14775)

This is being added alongside the new future.unstable_passthroughRequests future flag so that users still have a way to access the normalized URL when that flag is enabled and non-normalized request's are being passed to your handlers. When adopting this flag, you will only need to start leveraging this new parameter if you are relying on the normalization of request.url in your application code.

If you don't have the flag enabled, then unstable_url will match request.url.

`v7.13.1`

Compare Source

Patch Changes

fix null reference exception in bad codepath leading to invalid route tree comparisons (#14780)
fix: clear timeout when turbo-stream encoding completes (#14810)
Improve error message when Origin header is invalid (#14743)
Fix matchPath optional params matching without a "/" separator. (#14689)
- matchPath("/users/:id?", "/usersblah") now returns null.
- matchPath("/test_route/:part?", "/test_route_more") now returns null.
add RSC unstable_getRequest (#14758)
Fix HydrateFallback rendering during initial lazy route discovery with matching splat route (#14740)

[UNSTABLE] Add support for <Link unstable_mask> in Data Mode which allows users to navigate to a URL in the router but "mask" the URL displayed in the browser. This is useful for contextual routing usages such as displaying an image in a model on top of a gallery, but displaying a browser URL directly to the image that can be shared and loaded without the contextual gallery in the background. (#14716)

// routes/gallery.tsx
export function clientLoader({ request }: Route.LoaderArgs) {
  let sp = new URL(request.url).searchParams;
  return {
    images: getImages(),
    // When the router location has the image param, load the modal data
    modalImage: sp.has("image") ? getImage(sp.get("image")!) : null,
  };
}

export default function Gallery({ loaderData }: Route.ComponentProps) {
  return (
    <>
      <GalleryGrid>
        {loaderData.images.map((image) => (
          <Link
            key={image.id}
            {/* Navigate the router to /galley?image=N */}}
            to={`/gallery?image=${image.id}`}
            {/* But display /images/N in the URL bar */}}
            unstable_mask={`/images/${image.id}`}
          >
            <img src={image.url} alt={image.alt} />
          </Link>
        ))}
      </GalleryGrid>

      {/* When the modal data exists, display the modal */}
      {data.modalImage ? (
        <dialog open>
          <img src={data.modalImage.url} alt={data.modalImage.alt} />
        </dialog>
      ) : null}
    </>
  );
}

Notes:

The masked location, if present, will be available on useLocation().unstable_mask so you can detect whether you are currently masked or not.
Masked URLs only work for SPA use cases, and will be removed from history.state during SSR.
This provides a first-class API to mask URLs in Data Mode to achieve the same behavior you could do in Declarative Mode via manual backgroundLocation management.

RSC: Update failed origin checks to return a 400 status and appropriate UI instead of a generic 500 (#14755)
Preserve query parameters and hash on manifest version mismatch reload (#14813)

`v7.13.0`

Compare Source

Minor Changes

Add crossOrigin prop to Links component (#14687)

Patch Changes

Fix double slash normalization for useNavigate colon urls (#14718)
Update failed origin checks to return a 400 status instead of a 500 (#14737)
Bugfix #14666: Inline criticalCss is missing nonce (#14691)
Loosen allowedActionOrigins glob check so ** matches all domains (#14722)

`v7.12.0`

Compare Source

Minor Changes

Add additional layer of CSRF protection by rejecting submissions to UI routes from external origins. If you need to permit access to specific external origins, you can specify them in the react-router.config.ts config allowedActionOrigins field. (#14708)

Patch Changes

Fix generatePath when used with suffixed params (i.e., "/books/:id.json") (#14269)
Export UNSAFE_createMemoryHistory and UNSAFE_createHashHistory alongside UNSAFE_createBrowserHistory for consistency. These are not intended to be used for new apps but intended to help apps usiong unstable_HistoryRouter migrate from v6->v7 so they can adopt the newer APIs. (#14663)
Escape HTML in scroll restoration keys (#14705)
Validate redirect locations (#14706)
[UNSTABLE] Pass <Scripts nonce> value through to the underlying importmap script tag when using future.unstable_subResourceIntegrity (#14675)
[UNSTABLE] Add a new future.unstable_trailingSlashAwareDataRequests flag to provide consistent behavior of request.pathname inside middleware, loader, and action functions on document and data requests when a trailing slash is present in the browser URL. (#14644)

Currently, your HTTP and request pathnames would be as follows for /a/b/c and /a/b/c/

URL /a/b/c HTTP pathname request pathname`

Document /a/b/c /a/b/c ✅

Data /a/b/c.data /a/b/c ✅

URL /a/b/c/ HTTP pathname request pathname`

Document /a/b/c/ /a/b/c/ ✅

Data /a/b/c.data /a/b/c ⚠️

With this flag enabled, these pathnames will be made consistent though a new _.data format for client-side .data requests:

URL /a/b/c HTTP pathname request pathname`

Document /a/b/c /a/b/c ✅

Data /a/b/c.data /a/b/c ✅

URL /a/b/c/ HTTP pathname request pathname`

Document /a/b/c/ /a/b/c/ ✅

Data /a/b/c/_.data ⬅️ /a/b/c/ ✅

This a bug fix but we are putting it behind an opt-in flag because it has the potential to be a "breaking bug fix" if you are relying on the URL format for any other application or caching logic.

Enabling this flag also changes the format of client side .data requests from /_root.data to /_.data when navigating to / to align with the new format. This does not impact the request pathname which is still / in all cases.
Preserve clientLoader.hydrate=true when using <HydratedRouter unstable_instrumentations> (#14674)

`v7.11.0`

Compare Source

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)

`v7.10.1`

Compare Source

Patch Changes

Update the useOptimistic stub we provide for React 18 users to use a stable setter function to avoid potential useEffect loops - specifically when using <Link viewTransition> (#14628)

`v7.10.0`

Compare Source

Minor Changes

Stabilize fetcher.reset() (#14545)
- ⚠️ This is a breaking change if you have begun using fetcher.unstable_reset()
Stabilize the dataStrategy match.shouldRevalidateArgs/match.shouldCallHandler() APIs. (#14592)
- The match.shouldLoad API is now marked deprecated in favor of these more powerful alternatives
- If you're using this API in a custom dataStrategy today, you can swap to the new API at your convenience:
```
// Before
const matchesToLoad = matches.filter((m) => m.shouldLoad);

// After
const matchesToLoad = matches.filter((m) => m.shouldCallHandler());
```
- match.shouldRevalidateArgs is the argument that will be passed to the route shouldRevaliate function
- Combined with the parameter accepted by match.shouldCallHandler, you can define a custom revalidation behavior for your dataStrategy:
```
const matchesToLoad = matches.filter((m) => {
  const defaultShouldRevalidate = customRevalidationBehavior(
    match.shouldRevalidateArgs,
  );
  return m.shouldCallHandler(defaultShouldRevalidate);
  // The argument here will override the internal `defaultShouldRevalidate` value
});
```

Patch Changes

Fix a Framework Mode bug where the defaultShouldRevalidate parameter to shouldRevalidate would not be correct after action returned a 4xx/5xx response (true when it should have been false) (#14592)
- If your shouldRevalidate function relied on that parameter, you may have seen unintended revalidations
Fix fetcher.submit failing with plain objects containing a tagName property (#14534)
[UNSTABLE] Add unstable_pattern to the parameters for client side unstable_onError, refactor how it's called by RouterProvider to avoid potential strict mode issues (#14573)
Add new unstable_useTransitions flag to routers to give users control over the usage of React.startTransition and React.useOptimistic. (#14524)
- Framework Mode + Data Mode:
  - <HydratedRouter unstable_transition>/<RouterProvider unstable_transition>
  - When left unset (current default behavior)
    - Router state updates are wrapped in React.startTransition
    - ⚠️ This can lead to buggy behaviors if you are wrapping your own navigations/fetchers in React.startTransition
    - You should set the

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot requested a review from charIeszhao as a code owner December 5, 2024 05:13

renovate bot force-pushed the renovate/major-react-router-monorepo branch 4 times, most recently from 278cde3 to 9a043d6 Compare December 9, 2024 09:43

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 9a043d6 to 9080354 Compare April 2, 2025 03:29

renovate bot force-pushed the renovate/major-react-router-monorepo branch 4 times, most recently from db2ace5 to 22d2fcb Compare May 14, 2025 06:33

renovate bot force-pushed the renovate/major-react-router-monorepo branch 4 times, most recently from 3b9b32d to 0477b9c Compare May 28, 2025 10:05

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from d267e6f to d513e92 Compare June 19, 2025 03:21

renovate bot force-pushed the renovate/major-react-router-monorepo branch from d513e92 to 673b0a9 Compare July 24, 2025 20:40

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from b9678fc to 5e565d4 Compare August 7, 2025 21:07

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from fb51f8d to c29c93d Compare August 19, 2025 13:15

renovate bot force-pushed the renovate/major-react-router-monorepo branch from c29c93d to 3c4da56 Compare August 24, 2025 04:15

renovate bot force-pushed the renovate/major-react-router-monorepo branch 4 times, most recently from e90a7e6 to 79b7b51 Compare September 3, 2025 03:50

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 79b1dfc to 575695e Compare September 18, 2025 07:34

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 26501ca to a8577fa Compare September 25, 2025 21:41

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from d9a3a2a to 9b53b6f Compare November 20, 2025 07:29

renovate bot force-pushed the renovate/major-react-router-monorepo branch 3 times, most recently from 7249d83 to aad3058 Compare December 4, 2025 18:46

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 605d7e9 to b91e183 Compare December 17, 2025 18:03

renovate bot force-pushed the renovate/major-react-router-monorepo branch from b91e183 to 0bb2f5f Compare December 31, 2025 15:47

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from a466eaf to 29cfbfd Compare January 8, 2026 18:39

renovate bot force-pushed the renovate/major-react-router-monorepo branch 8 times, most recently from 977947c to 4c4d6e8 Compare January 23, 2026 20:35

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 4c4d6e8 to a3167c7 Compare February 2, 2026 03:31

renovate bot force-pushed the renovate/major-react-router-monorepo branch from a3167c7 to 13f57ac Compare February 9, 2026 07:55

renovate bot force-pushed the renovate/major-react-router-monorepo branch 3 times, most recently from ab38f9a to 876767f Compare February 24, 2026 07:44

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 315aed9 to 6f21ed1 Compare March 5, 2026 03:21

renovate bot changed the title ~~fix(deps): update dependency react-router-dom to v7~~ fix(deps): update react-router monorepo to v7 (major) Mar 5, 2026

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 6f21ed1 to 8dfee4f Compare March 23, 2026 13:59

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 8dfee4f to 0664a11 Compare April 1, 2026 19:02

fix(deps): update react-router monorepo to v7

323f7e4

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 0664a11 to 323f7e4 Compare April 2, 2026 22:14

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update react-router monorepo to v7 (major)#875

fix(deps): update react-router monorepo to v7 (major)#875
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-react-router-monorepo

renovate bot commented Dec 5, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

0 participants

Server Component Export	Client Component
`ServerComponent`	`default`
`ServerErrorBoundary`	`ErrorBoundary`
`ServerLayout`	`Layout`
`ServerHydrateFallback`	`HydrateFallback`

URL `/a/b/c`	HTTP pathname	`request` pathname`
Document	`/a/b/c`	`/a/b/c` ✅
Data	`/a/b/c.data`	`/a/b/c` ✅

URL `/a/b/c/`	HTTP pathname	`request` pathname`
Document	`/a/b/c/`	`/a/b/c/` ✅
Data	`/a/b/c.data`	`/a/b/c` ⚠️

Uh oh!

Conversation

renovate bot commented Dec 5, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

v6.4.4: v6.4.4

renovate bot commented Dec 5, 2024 •

edited

Loading

`v6.4.4`: v6.4.4