fix(deps): update react-router monorepo to v6.29.0 #639

renovate · 2024-01-08T08:06:25Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router (source)	`6.18.0` -> `6.29.0`
react-router-dom (source)	`6.18.0` -> `6.29.0`

Release Notes

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

Minor Changes

- Log deprecation warnings for v7 flags (#11750)
- Add deprecation warnings to json/defer in favor of returning raw objects
  - These methods will be removed in React Router v7

Patch Changes

Update JSDoc URLs for new website structure (add /v6/ segment) (#12141)
Updated dependencies:
- @remix-run/[email protected]

`v6.27.0`: v6.27.0

Compare Source

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6270

`v6.26.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v6.26.1`

Compare Source

`v6.26.0`

Compare Source

Minor Changes

Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#11811)

Patch Changes

Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#11838)
- During initial hydration, router.state.matches will now include any partial matches so that we can render ancestor HydrateFallback components
Updated dependencies:
- @remix-run/[email protected]

`v6.25.1`: v6.25.1

Compare Source

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6251

`v6.25.0`

Compare Source

Minor Changes

Stabilize future.unstable_skipActionErrorRevalidation as future.v7_skipActionErrorRevalidation (#11769)
- When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a Response with a 4xx/5xx status code
- You may still opt-into revalidation via shouldRevalidate
- This also changes shouldRevalidate's unstable_actionStatus parameter to actionStatus

Patch Changes

Fix regression and properly decode paths inside useMatch so matches/params reflect decoded params (#11789)
Updated dependencies:
- @remix-run/[email protected]

`v6.24.1`

Compare Source

Patch Changes

When using future.v7_relativeSplatPath, properly resolve relative paths in splat routes that are children of pathless routes (#11633)
Updated dependencies:
- @remix-run/[email protected]

`v6.24.0`

Compare Source

Minor Changes

Add support for Lazy Route Discovery (a.k.a. Fog of War) (#11626)
- RFC: https://redirect.github.com/remix-run/react-router/discussions/11113
- unstable_patchRoutesOnMiss docs: https://reactrouter.com/en/main/routers/create-browser-router

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v6.23.1`

Compare Source

Patch Changes

allow undefined to be resolved with <Await> (#11513)
Updated dependencies:
- @remix-run/[email protected]

`v6.23.0`

Compare Source

Minor Changes

Add a new unstable_dataStrategy configuration option (#11098)
- This option allows Data Router applications to take control over the approach for executing route loaders and actions
- The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v6.22.3`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v6.22.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v6.22.1`: v6.22.1

Compare Source

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6221

`v6.22.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]

`v6.21.3`

Compare Source

Patch Changes

Remove leftover unstable_ prefix from Blocker/BlockerFunction types (#11187)

`v6.21.2`

Compare Source

`v6.21.1`

Compare Source

Patch Changes

Fix bug with route.lazy not working correctly on initial SPA load when v7_partialHydration is specified (#11121)
Updated dependencies:
- @remix-run/[email protected]

`v6.21.0`

Compare Source

Minor Changes

Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#11087)

This fix was originally added in #10983 and was later reverted in #11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #11052)

The Bug
The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

The Background
This decision was originally made thinking that it would make the concept of nested different sections of your apps in <Routes> easier if relative routing would replace the current splat:

<BrowserRouter>
  <Routes>
    <Route path="/" element={<Home />} />
    <Route path="dashboard/*" element={<Dashboard />} />
  </Routes>
</BrowserRouter>

Any paths like /dashboard, /dashboard/team, /dashboard/projects will match the Dashboard route. The dashboard component itself can then render nested <Routes>:

function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="/">Dashboard Home</Link>
        <Link to="team">Team</Link>
        <Link to="projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Routes>
    </div>
  );
}

Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the Dashboard as its own independent app, or embed it into your large app without making any changes to it.

The Problem

The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that "." always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using ".":

// If we are on URL /dashboard/team, and we want to link to /dashboard/team:
function DashboardTeam() {
  // ❌ This is broken and results in <a href="/dashboard">
  return <Link to=".">A broken link to the Current URL</Link>;

  // ✅ This is fixed but super unintuitive since we're already at /dashboard/team!
  return <Link to="./team">A broken link to the Current URL</Link>;
}

We've also introduced an issue that we can no longer move our DashboardTeam component around our route hierarchy easily - since it behaves differently if we're underneath a non-splat route, such as /dashboard/:widget. Now, our "." links will, properly point to ourself inclusive of the dynamic param value so behavior will break from it's corresponding usage in a /dashboard/* route.

Even worse, consider a nested splat route configuration:

<BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

Now, a <Link to="."> and a <Link to=".."> inside the Dashboard component go to the same place! That is definitely not correct!

Another common issue arose in Data Routers (and Remix) where any <Form> should post to it's own route action if you the user doesn't specify a form action:

let router = createBrowserRouter({
  path: "/dashboard",
  children: [
    {
      path: "*",
      action: dashboardAction,
      Component() {
        // ❌ This form is broken!  It throws a 405 error when it submits because
        // it tries to submit to /dashboard (without the splat value) and the parent
        // `/dashboard` route doesn't have an action
        return <Form method="post">...</Form>;
      },
    },
  ],
});

This is just a compounded issue from the above because the default location for a Form to submit to is itself (".") - and if we ignore the splat portion, that now resolves to the parent route.

The Solution
If you are leveraging this behavior, it's recommended to enable the future flag, move your splat to it's own route, and leverage ../ for any links to "sibling" pages:

<BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route index path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="..">Dashboard Home</Link>
        <Link to="../team">Team</Link>
        <Link to="../projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Router>
    </div>
  );
}

This way, . means "the full current pathname for my route" in all cases (including static, dynamic, and splat routes) and .. always means "my parents pathname".

Patch Changes

Properly handle falsy error values in ErrorBoundary's (#11071)
Updated dependencies:
- @remix-run/[email protected]

`v6.20.1`

Compare Source

Patch Changes

Revert the useResolvedPath fix for splat routes due to a large number of applications that were relying on the buggy behavior (see https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329). We plan to re-introduce this fix behind a future flag in the next minor version. (#11078)
Updated dependencies:
- @remix-run/[email protected]

`v6.20.0`

Compare Source

Minor Changes

Export the PathParam type from the public API (#10719)

Patch Changes

Fix bug with resolveTo in splat routes (#11045)
- This is a follow up to #10983 to handle the few other code paths using getPathContributingMatches
- This removes the UNSAFE_getPathContributingMatches export from @remix-run/router since we no longer need this in the react-router/react-router-dom layers
Updated dependencies:
- @remix-run/[email protected]

`v6.19.0`

Compare Source

Minor Changes

Add unstable_flushSync option to useNavigate/useSumbit/fetcher.load/fetcher.submit to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#11005)
Remove the unstable_ prefix from the useBlocker hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix from unstable_usePrompt due to differences in how browsers handle window.confirm that prevent React Router from guaranteeing consistent/correct behavior. (#10991)

Patch Changes

Fix useActionData so it returns proper contextual action data and not any action data in the tree (#11023)
Fix bug in useResolvedPath that would cause useResolvedPath(".") in a splat route to lose the splat portion of the URL path. (#10983)
- ⚠️ This fixes a quite long-standing bug specifically for "." paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via "." inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.
Updated dependencies:
- @remix-run/[email protected]

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

`v6.29.0`

Compare Source

`v6.28.2`

Compare Source

`v6.28.1`

Compare Source

`v6.28.0`

Compare Source

Minor Changes

- Log deprecation warnings for v7 flags (#11750)
- Add deprecation warnings to json/defer in favor of returning raw objects
  - These methods will be removed in React Router v7

Patch Changes

Update JSDoc URLs for new website structure (add /v6/ segment) (#12141)
Updated dependencies:
- [email protected]
- @remix-run/[email protected]

`v6.27.0`

Compare Source

`v6.26.2`

Compare Source

`v6.26.1`

Compare Source

`v6.26.0`

Compare Source

Minor Changes

Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#11811)

Patch Changes

Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#11838)
- During initial hydration, router.state.matches will now include any partial matches so that we can render ancestor HydrateFallback components
Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.25.1`

Compare Source

Patch Changes

Memoize some RouterProvider internals to reduce unnecessary re-renders (#11803)
Updated dependencies:
- [email protected]

`v6.25.0`

Compare Source

Minor Changes

Stabilize future.unstable_skipActionErrorRevalidation as future.v7_skipActionErrorRevalidation (#11769)
- When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a Response with a 4xx/5xx status code
- You may still opt-into revalidation via shouldRevalidate
- This also changes shouldRevalidate's unstable_actionStatus parameter to actionStatus

Patch Changes

Updated dependencies:
- [email protected]
- @remix-run/[email protected]

`v6.24.1`

Compare Source

Patch Changes

Remove polyfill.io reference from warning message because the domain was sold and has since been determined to serve malware (#11741)
- See https://sansec.io/research/polyfill-supply-chain-attack
Export NavLinkRenderProps type for easier typing of custom NavLink callback (#11553)
Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.24.0`

Compare Source

Minor Changes

Add support for Lazy Route Discovery (a.k.a. Fog of War) (#11626)
- RFC: https://redirect.github.com/remix-run/react-router/discussions/11113
- unstable_patchRoutesOnMiss docs: https://reactrouter.com/en/main/routers/create-browser-router

Patch Changes

Fix fetcher.submit types - remove incorrect navigate/fetcherKey/unstable_viewTransition options because they are only relevant for useSubmit (#11631)
Allow falsy location.state values passed to <StaticRouter> (#11495)
Updated dependencies:
- [email protected]
- @remix-run/[email protected]

`v6.23.1`

Compare Source

Patch Changes

Check for document existence when checking startViewTransition (#11544)
Change the react-router-dom/server import back to react-router-dom instead of index.ts (#11514)
Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.23.0`

Compare Source

Minor Changes

Add a new unstable_dataStrategy configuration option (#11098)
- This option allows Data Router applications to take control over the approach for executing route loaders and actions
- The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more

Patch Changes

Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.22.3`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.22.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.22.1`

Compare Source

`v6.22.0`

Compare Source

Minor Changes

Include a window__reactRouterVersion tag for CWV Report detection (#11222)

Patch Changes

Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.21.3`

Compare Source

Patch Changes

Fix NavLink isPending when a basename is used (#11195)
Remove leftover unstable_ prefix from Blocker/BlockerFunction types (#11187)
Updated dependencies:
- [email protected]

`v6.21.2`

Compare Source

`v6.21.1`

Compare Source

Patch Changes

Updated dependencies:
- [email protected]
- @remix-run/[email protected]

`v6.21.0`

Compare Source

Minor Changes

Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#11087)

This fix was originally added in #10983 and was later reverted in #11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #11052)

The Bug
The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

The Background
This decision was originally made thinking that it would make the concept of nested different sections of your apps in <Routes> easier if relative routing would replace the current splat:

<BrowserRouter>
  <Routes>
    <Route path="/" element={<Home />} />
    <Route path="dashboard/*" element={<Dashboard />} />
  </Routes>
</BrowserRouter>

Any paths like /dashboard, /dashboard/team, /dashboard/projects will match the Dashboard route. The dashboard component itself can then render nested <Routes>:

function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="/">Dashboard Home</Link>
        <Link to="team">Team</Link>
        <Link to="projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Routes>
    </div>
  );
}

Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the Dashboard as its own independent app, or embed it into your large app without making any changes to it.

The Problem

The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that "." always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using ".":

// If we are on URL /dashboard/team, and we want to link to /dashboard/team:
function DashboardTeam() {
  // ❌ This is broken and results in <a href="/dashboard">
  return <Link to=".">A broken link to the Current URL</Link>;

  // ✅ This is fixed but super unintuitive since we're already at /dashboard/team!
  return <Link to="./team">A broken link to the Current URL</Link>;
}

We've also introduced an issue that we can no longer move our DashboardTeam component around our route hierarchy easily - since it behaves differently if we're underneath a non-splat route, such as /dashboard/:widget. Now, our "." links will, properly point to ourself inclusive of the dynamic param value so behavior will break from it's corresponding usage in a /dashboard/* route.

Even worse, consider a nested splat route configuration:

<BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

Now, a <Link to="."> and a <Link to=".."> inside the Dashboard component go to the same place! That is definitely not correct!

Another common issue arose in Data Routers (and Remix) where any <Form> should post to it's own route action if you the user doesn't specify a form action:

let router = createBrowserRouter({
  path: "/dashboard",
  children: [
    {
      path: "*",
      action: dashboardAction,
      Component() {
        // ❌ This form is broken!  It throws a 405 error when it submits because
        // it tries to submit to /dashboard (without the splat value) and the parent
        // `/dashboard` route doesn't have an action
        return <Form method="post">...</Form>;
      },
    },
  ],
});

This is just a compounded issue from the above because the default location for a Form to submit to is itself (".") - and if we ignore the splat portion, that now resolves to the parent route.

The Solution
If you are leveraging this behavior, it's recommended to enable the future flag, move your splat to it's own route, and leverage ../ for any links to "sibling" pages:

<BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route index path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="..">Dashboard Home</Link>
        <Link to="../team">Team</Link>
        <Link to="../projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Router>
    </div>
  );
}

This way, . means "the full current pathname for my route" in all cases (including static, dynamic, and splat routes) and .. always means "my parents pathname".

Patch Changes

Updated dependencies:
- @remix-run/[email protected]
- [email protected]

`v6.20.1`

Compare Source

Patch Changes

Revert the useResolvedPath fix for splat routes due to a large number of applications that were relying on the buggy behavior (see https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329). We plan to re-introduce this fix behind a future flag in the next minor version. (#11078)
Updated dependencies:
- [email protected]
- @remix-run/[email protected]

`v6.20.0`

Compare Source

Minor Changes

Export the PathParam type from the public API (#10719)

Patch Changes

Updated dependencies:
- [email protected]
- @remix-run/[email protected]

`v6.19.0`

Compare Source

Minor Changes

Add unstable_flushSync option to useNavigate/useSumbit/fetcher.load/fetcher.submit to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#11005)
Allow unstable_usePrompt to accept a BlockerFunction in addition to a boolean (#10991)

Patch Changes

Fix issue where a changing fetcher key in a useFetcher that remains mounted wasn't getting picked up (#11009)
Fix useFormAction which was incorrectly inheriting the ?index query param from child route action submissions (#11025)
Fix NavLink active logic when to location has a trailing slash (#10734)
Updated dependencies:
- [email protected]
- @remix-run/[email protected]

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

codecov · 2024-01-08T08:14:18Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.17%. Comparing base (58aa512) to head (7e1160f).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #639   +/-   ##
=======================================
  Coverage   93.17%   93.17%           
=======================================
  Files         161      161           
  Lines        3401     3401           
  Branches      924      914   -10     
=======================================
  Hits         3169     3169           
- Misses        214      215    +1     
+ Partials       18       17    -1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

renovate bot force-pushed the renovate/react-router-monorepo branch from c809bb6 to 8df2de7 Compare January 9, 2024 07:32

sundasnoreen12 added the On Hold label Jan 9, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch 4 times, most recently from 8d82b01 to 7520859 Compare January 11, 2024 16:22

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.21.1~~ fix(deps): update react-router monorepo Jan 11, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from 7520859 to d5673ed Compare January 11, 2024 20:24

renovate bot changed the title ~~fix(deps): update react-router monorepo~~ fix(deps): update react-router monorepo to v6.21.2 Jan 11, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch 6 times, most recently from 009b67b to 1360478 Compare January 18, 2024 22:45

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.21.2~~ fix(deps): update react-router monorepo to v6.21.3 Jan 18, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch 3 times, most recently from 4bbccf0 to 78479e4 Compare January 25, 2024 13:59

renovate bot force-pushed the renovate/react-router-monorepo branch 5 times, most recently from 9e1ab9d to 64c3fd8 Compare February 1, 2024 21:55

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.21.3~~ fix(deps): update react-router monorepo to v6.22.0 Feb 1, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from 64c3fd8 to 5e97cc4 Compare February 2, 2024 22:01

renovate bot force-pushed the renovate/react-router-monorepo branch 3 times, most recently from 728acea to bb199e5 Compare February 16, 2024 21:26

renovate bot force-pushed the renovate/react-router-monorepo branch from 0f699bc to a1c69b2 Compare July 17, 2024 20:13

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.25.0~~ fix(deps): update react-router monorepo to v6.25.1 Jul 17, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from a1c69b2 to 2406d2d Compare July 24, 2024 12:27

renovate bot force-pushed the renovate/react-router-monorepo branch from 2406d2d to 5a504d6 Compare August 2, 2024 12:18

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.25.1~~ fix(deps): update react-router monorepo to v6.26.0 Aug 2, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from 5a504d6 to 3ce6320 Compare August 8, 2024 13:16

renovate bot force-pushed the renovate/react-router-monorepo branch from 3ce6320 to a55cb38 Compare August 15, 2024 17:47

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.26.0~~ fix(deps): update react-router monorepo to v6.26.1 Aug 15, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from a55cb38 to 4597d72 Compare August 22, 2024 18:41

renovate bot force-pushed the renovate/react-router-monorepo branch 2 times, most recently from 8407798 to e93497f Compare September 9, 2024 15:59

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.26.1~~ fix(deps): update react-router monorepo to v6.26.2 Sep 9, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from e93497f to ff816d5 Compare September 10, 2024 09:40

renovate bot force-pushed the renovate/react-router-monorepo branch from ff816d5 to 9818226 Compare October 11, 2024 19:36

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.26.2~~ fix(deps): update react-router monorepo to v6.27.0 Oct 11, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch 2 times, most recently from 151e504 to bbe8135 Compare October 22, 2024 23:22

renovate bot force-pushed the renovate/react-router-monorepo branch 2 times, most recently from aeeb51a to 72912d6 Compare November 7, 2024 00:58

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.27.0~~ fix(deps): update react-router monorepo to v6.28.0 Nov 7, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from 72912d6 to 6b9a1af Compare November 21, 2024 12:45

renovate bot force-pushed the renovate/react-router-monorepo branch from 6b9a1af to 9d02b22 Compare December 10, 2024 07:22

renovate bot force-pushed the renovate/react-router-monorepo branch from 9d02b22 to 67be843 Compare December 20, 2024 21:29

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.28.0~~ fix(deps): update react-router monorepo to v6.28.1 Dec 20, 2024

renovate bot force-pushed the renovate/react-router-monorepo branch from 67be843 to 557eee1 Compare January 16, 2025 18:08

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.28.1~~ fix(deps): update react-router monorepo to v6.28.2 Jan 16, 2025

renovate bot force-pushed the renovate/react-router-monorepo branch from 557eee1 to e8369aa Compare January 17, 2025 16:15

fix(deps): update react-router monorepo to v6.29.0

7e1160f

renovate bot force-pushed the renovate/react-router-monorepo branch from e8369aa to 7e1160f Compare January 30, 2025 18:01

renovate bot changed the title ~~fix(deps): update react-router monorepo to v6.28.2~~ fix(deps): update react-router monorepo to v6.29.0 Jan 30, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update react-router monorepo to v6.29.0 #639

fix(deps): update react-router monorepo to v6.29.0 #639

renovate bot commented Jan 8, 2024 •

edited

Loading

codecov bot commented Jan 8, 2024 •

edited

Loading

fix(deps): update react-router monorepo to v6.29.0 #639

Are you sure you want to change the base?

fix(deps): update react-router monorepo to v6.29.0 #639

Conversation

renovate bot commented Jan 8, 2024 • edited Loading

Release Notes

v6.29.0: v6.29.0

v6.28.2: v6.28.2

v6.28.1: v6.28.1

Minor Changes

Patch Changes

v6.27.0: v6.27.0

Patch Changes

Minor Changes

Patch Changes

v6.25.1: v6.25.1

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

v6.22.1: v6.22.1

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

codecov bot commented Jan 8, 2024 • edited Loading

Codecov Report

renovate bot commented Jan 8, 2024 •

edited

Loading

`v6.29.0`: v6.29.0

`v6.28.2`: v6.28.2

`v6.28.1`: v6.28.1

`v6.27.0`: v6.27.0

`v6.25.1`: v6.25.1

`v6.22.1`: v6.22.1

codecov bot commented Jan 8, 2024 •

edited

Loading