fix(deps): update dependency react-router-dom to v7 #423

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

`v6.2.2`

Compare Source

What's Changed

🐛 Bug Fixes

Fixed nested splat routes that begin with special URL-safe characters (#8563)
Fixed a bug where index routes were missing route context in some cases (#8497)

New Contributors

@chasinhues made their first contribution in #8514
@underager made their first contribution in #8531
@kantuni made their first contribution in #8537
@ArjaanBuijk made their first contribution in #8536
@jmargeta made their first contribution in #8548
@koojaa made their first contribution in #8542
@chrisngobanh made their first contribution in #8576
@ChristopherChudzicki made their first contribution in #8582
@awreese made their first contribution in #8596
@bhbs made their first contribution in #8601
@LukerSpringtree made their first contribution in #8619
@hsbtr made their first contribution in #8476
@abhi-kr-2100 made their first contribution in #8658
@cvbuelow made their first contribution in #8663
@hyesungoh made their first contribution in #8666
@BrianT1414 made their first contribution in #8667
@IbraRouisDev made their first contribution in #8683
@shihanng made their first contribution in #8689
@latin-1 made their first contribution in #8529
@Isammoc made their first contribution in #8533
@KutnerUri made their first contribution in #8278
@shamsup made their first contribution in #8563
@brophdawg11 made their first contribution in #8691

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

`v6.2.1`

Compare Source

This release updates the internal history dependency to 5.2.0.

Full Changelog: remix-run/react-router@v6.2.0...v6.2.1

`v6.2.0`

Compare Source

🐛 Bug fixes

Fixed the RouteProps element type, which should be a ReactNode (#8473)
Fixed a bug with useOutlet for top-level routes (#8483)

✨ Features

We now use statically analyzable CJS exports. This enables named imports in Node ESM scripts (See the commit).

New Contributors

@thisiskartik made their first contribution in #8487
@vijaypushkin made their first contribution in #8491

Full Changelog: remix-run/react-router@v6.1.1...v6.2.0

`v6.1.1`

Compare Source

In v6.1.0 we inadvertently shipped a new, undocumented API that will likely introduce bugs (#7586). We have flagged HistoryRouter as unstable_HistoryRouter, as this API will likely need to change before a new major release.

Full Changelog: remix-run/react-router@v6.1.0...v6.1.1

`v6.1.0`

Compare Source

🐛 Bug fixes

Fixed a bug that broke support for base64 encoded IDs on nested routes (#8291)

✨ Features

<Outlet> can now receive a context prop. This value is passed to child routes and is accessible via the new useOutletContext hook. See the API docs for details. (#8461)
<NavLink> can now receive a child function for access to its props. (#8164)

💅 Enhancements

Improved TypeScript signature for useMatch and matchPath. For example, when you call useMatch("foo/:bar/:baz"), the path is parsed and the return type will be PathMatch<"bar" | "baz">. (#8030)
A few error message improvements (#8202)

New Contributors

@rwieruch made their first contribution in #8244
@codeiotic made their first contribution in #8247
@Sannnao made their first contribution in #8263
@mattmazzola made their first contribution in #8255
@ngokevin made their first contribution in #8267
@TimisRobert made their first contribution in #8269
@mikeldking made their first contribution in #8279
@fishmandev made their first contribution in #8289
@rjerue made their first contribution in #8304
@rockingskier made their first contribution in #8314
@arinthros made their first contribution in #8337
@noisypigeon made their first contribution in #8361
@elylucas made their first contribution in #8368
@paulsmithkc made their first contribution in #8357
@sanketshah19 made their first contribution in #8372
@JakubDrozd made their first contribution in #8402
@markivancho made their first contribution in #8414
@turansky made their first contribution in #8420
@shivamsinghchahar made their first contribution in #8423
@petersendidit made their first contribution in #8436
@Ajayff4 made their first contribution in #8373
@RobHannay made their first contribution in #8455
@kddnewton made their first contribution in #8030
@brockross made their first contribution in #8462
@sergiodxa made their first contribution in #8164
@baozouai made their first contribution in #8171
@liuhanqu made their first contribution in #8374

Full Changelog: remix-run/react-router@v6.0.1...v6.1.0

`v6.0.2`

Compare Source

✨ Features

Added the reloadDocument prop to <Link>. This allows <Link> to function like a normal anchor tag by reloading the document after navigation while maintaining the relative to resolution.

🗒️ Docs

Fixed several issues in docblocks and the docs themselves. See the full changelog for the deets!

🤝 New Contributors

@rwieruch made their first contribution in #8244
@ProProgrammer2504 made their first contribution in #8247
@Sannnao made their first contribution in #8263
@mattmazzola made their first contribution in #8255
@ngokevin made their first contribution in #8267
@TimisRobert made their first contribution in #8269
@mikeldking made their first contribution in #8279
@fishmandev made their first contribution in #8289

Full Changelog

`v6.0.1`

Compare Source

🐛 Bug Fixes

Add a default <StaticRouter location> value (#8243)
Add invariant for using <Route> inside <Routes> to help people make the change (#8238)

`v6.0.0`

Compare Source

React Router v6 is here!

Please go read our blog post for more information on all the great stuff in v6 including notes about how to upgrade from React Router v5 and Reach Router.

`v5.3.4`

Compare Source

We removed the mini-create-react-context dependency, moving it into an internal module to eliminate peer dependency warnings for users on React 18 (#9382).

Full Changelog: remix-run/react-router@v5.3.3...v5.3.4

`v5.3.3`

Compare Source

This release fixes a bad version selector in react-router-native.

`v5.3.2`

Compare Source

Fix: make v5 Router compatible with v18 StrictMode by @jgoz in #8831

`v5.3.1`

Compare Source

This release adds missing LICENSE files to the published build.

`v5.3.0`

Compare Source

This release of react-router-dom adds support for passing a function to either the className or style props to conditionally apply values based on the link's active state.

This provides similar functionality as the existing activeClassName and activeStyle props, but is a bit more powerful. For example, you can now easily apply styles exclusively to an inactive NavLink as well. This offers a nicer experience for folks who use utility class-based CSS tools such as Tailwind.

function Comp() {
  return (
    <NavLink
      to="/"
      className={isActive =>
        `px-3 py-2 ${isActive ? 'text-gray-200' : 'text-gray-800'}`
      }
    >
      Home
    </NavLink>
  );
}

Note that as of v6.0.0-beta.3, the activeClassName and activeStyle props are removed completely. Adding support for functional className and style props to both v5 and v6 will give v5 users an easier upgrade path.

Thanks to @tim-phillips for raising the issue that inspired the change! 🥳

`v5.2.1`

Compare Source

This release fixes a bug with <Link> so that, when the to location is the same as the current, the history state entry is replaced instead of pushed to the stack. See #5362 for details. 🥳

Thanks to @guidobouman for the PR and for everyone else who weighed in for the fix!

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 this update 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 · 2022-08-29T15:20:24Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: web/package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @jimp/plugin-threshold@0.10.3
npm WARN Found: @jimp/plugin-color@0.6.8
npm WARN node_modules/@jimp/plugin-color
npm WARN   @jimp/plugin-color@"^0.6.8" from @jimp/plugins@0.6.8
npm WARN   node_modules/@jimp/plugins
npm WARN     @jimp/plugins@"^0.6.8" from jimp@0.6.8
npm WARN     node_modules/jimp
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @jimp/plugin-color@">=0.8.0" from @jimp/plugin-threshold@0.10.3
npm WARN node_modules/@jimp/plugin-threshold
npm WARN   @jimp/plugin-threshold@"^0.10.3" from @jimp/plugins@0.10.3
npm WARN   node_modules/potrace/node_modules/@jimp/plugins
npm WARN 
npm WARN Conflicting peer dependency: @jimp/plugin-color@0.22.12
npm WARN node_modules/@jimp/plugin-color
npm WARN   peer @jimp/plugin-color@">=0.8.0" from @jimp/plugin-threshold@0.10.3
npm WARN   node_modules/@jimp/plugin-threshold
npm WARN     @jimp/plugin-threshold@"^0.10.3" from @jimp/plugins@0.10.3
npm WARN     node_modules/potrace/node_modules/@jimp/plugins
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @jimp/plugin-threshold@0.10.3
npm WARN Found: @jimp/plugin-resize@0.6.8
npm WARN node_modules/@jimp/plugin-resize
npm WARN   peer @jimp/plugin-resize@">=0.3.5" from @jimp/plugin-contain@0.6.8
npm WARN   node_modules/@jimp/plugin-contain
npm WARN     @jimp/plugin-contain@"^0.6.8" from @jimp/plugins@0.6.8
npm WARN     node_modules/@jimp/plugins
npm WARN   5 more (@jimp/plugin-cover, @jimp/plugin-rotate, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @jimp/plugin-resize@">=0.8.0" from @jimp/plugin-threshold@0.10.3
npm WARN node_modules/@jimp/plugin-threshold
npm WARN   @jimp/plugin-threshold@"^0.10.3" from @jimp/plugins@0.10.3
npm WARN   node_modules/potrace/node_modules/@jimp/plugins
npm WARN 
npm WARN Conflicting peer dependency: @jimp/plugin-resize@0.22.12
npm WARN node_modules/@jimp/plugin-resize
npm WARN   peer @jimp/plugin-resize@">=0.8.0" from @jimp/plugin-threshold@0.10.3
npm WARN   node_modules/@jimp/plugin-threshold
npm WARN     @jimp/plugin-threshold@"^0.10.3" from @jimp/plugins@0.10.3
npm WARN     node_modules/potrace/node_modules/@jimp/plugins
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: eslint-watch@7.0.0
npm ERR! Found: eslint@8.2.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"8.2.0" from the root project
npm ERR!   peer eslint@">= 4.12.1" from babel-eslint@10.1.0
npm ERR!   node_modules/babel-eslint
npm ERR!     dev babel-eslint@"10.1.0" from the root project
npm ERR!   10 more (eslint-config-airbnb, eslint-config-airbnb-base, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=7 <8.0.0" from eslint-watch@7.0.0
npm ERR! node_modules/eslint-watch
npm ERR!   dev eslint-watch@"7.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=7 <8.0.0" from eslint-watch@7.0.0
npm ERR!   node_modules/eslint-watch
npm ERR!     dev eslint-watch@"7.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-23T16_01_28_847Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-23T16_01_28_847Z-debug-0.log

socket-security · 2022-08-29T15:20:45Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		`npm/@babel/traverse@7.18.9` has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2; >= 8.0.0-alpha.0 < 8.0.0-alpha.4 Patched version: 7.23.2 From: web/package-lock.json → `npm/babel-eslint@10.1.0` → `npm/@babel/core@7.11.6` → `npm/@babel/plugin-proposal-class-properties@7.10.4` → `npm/@babel/preset-env@7.11.5` → `npm/@babel/traverse@7.18.9` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@babel/traverse@7.18.9`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`npm/form-data@4.0.0` has a Critical CVE. CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 4.0.4 From: web/package-lock.json → `npm/axios@0.27.2` → `npm/form-data@4.0.0` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/form-data@4.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`npm/bitmap2vector@0.0.4` has a Git dependency. Dependency: imagetracerjs @git+https://github.com/jankovicsandras/imagetracerjs.git Location: Package overview From: web/package-lock.json → `npm/bitmap2vector@0.0.4` ℹ Read more on: This package \| This alert \| What are git dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Publish the git dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/bitmap2vector@0.0.4`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

socket-security · 2025-09-17T04:01:52Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/@babel/plugin-syntax-dynamic-import@7.8.3
	npm/@babel/plugin-proposal-class-properties@7.10.4
	npm/bitmap2vector@0.0.4
	npm/@babel/preset-react@7.10.4
	npm/@babel/plugin-transform-react-constant-elements@7.10.4
	npm/@babel/node@7.10.5
	npm/browser-sync@2.26.14
	npm/@babel/cli@7.11.6
	npm/axios@0.27.2
	npm/blob-to-buffer@1.2.8
	npm/babel-jest@26.6.3
	npm/babel-plugin-inline-import@3.0.0
	npm/@hot-loader/react-dom@16.13.0
	npm/@babel/plugin-transform-runtime@7.11.5
	npm/@babel/preset-env@7.11.5
	npm/autoprefixer@9.7.6
	npm/@babel/polyfill@7.11.5
	npm/@babel/core@7.11.6
	npm/babel-plugin-lodash@3.3.4
	npm/babel-plugin-transform-react-remove-prop-types@0.4.24
	npm/babel-plugin-add-module-exports@1.0.2
	npm/babel-loader@8.1.0
	npm/babel-eslint@10.1.0

View full report

renovate bot requested a review from moul as a code owner November 5, 2021 12:38

auto-add-label bot added the bug Something isn't working label Nov 5, 2021

trafico-bot bot added the 🔍 Ready for Review Pull Request is not reviewed yet label Nov 5, 2021

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from cc41b1b to e5f3f91 Compare November 9, 2021 22:44

renovate bot force-pushed the renovate/major-react-router-monorepo branch from e5f3f91 to 7ccd420 Compare March 7, 2022 13:43

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 7ccd420 to a733f32 Compare April 24, 2022 19:31

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 2419eef to 4d0e78a Compare August 4, 2022 21:05

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 4d0e78a to 52c13c8 Compare August 29, 2022 15:20

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 52c13c8 to 6270fd1 Compare September 13, 2022 23:31

renovate bot force-pushed the renovate/major-react-router-monorepo branch 3 times, most recently from b7e00f1 to f534a7a Compare September 27, 2022 21:03

renovate bot force-pushed the renovate/major-react-router-monorepo branch from f534a7a to 00c9e15 Compare October 5, 2022 21:22

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 00c9e15 to d776a4a Compare October 13, 2022 11:32

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 508cdbc to f661de8 Compare November 1, 2022 17:10

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from c09d714 to 8dc128d Compare December 7, 2022 18:35

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 8dc128d to 1266cde Compare March 16, 2023 18:08

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 1266cde to 104e6d1 Compare March 30, 2023 01:09

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from f1cfe41 to 5d1c940 Compare May 3, 2023 23:22

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 5d1c940 to a681328 Compare May 17, 2023 19:58

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 777bd1c to 3c9cb9b Compare June 8, 2023 20:41

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 3c9cb9b to 2451303 Compare June 14, 2023 16:58

renovate bot force-pushed the renovate/major-react-router-monorepo branch from d2cab3a to c6ef876 Compare November 22, 2024 08:33

renovate bot changed the title ~~fix(deps): update dependency react-router-dom to v6~~ fix(deps): update dependency react-router-dom to v7 Nov 22, 2024

renovate bot force-pushed the renovate/major-react-router-monorepo branch from c6ef876 to b366592 Compare November 22, 2024 17:09

renovate bot force-pushed the renovate/major-react-router-monorepo branch from b366592 to d6e3a84 Compare December 3, 2024 05:39

renovate bot force-pushed the renovate/major-react-router-monorepo branch from d6e3a84 to 349a516 Compare December 20, 2024 21:07

renovate bot changed the title ~~fix(deps): update dependency react-router-dom to v7~~ fix(deps): update dependency react-router-dom to v6 Dec 20, 2024

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 349a516 to 483ee18 Compare December 21, 2024 01:15

renovate bot changed the title ~~fix(deps): update dependency react-router-dom to v6~~ fix(deps): update dependency react-router-dom to v7 Dec 21, 2024

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 483ee18 to 55f448a Compare December 23, 2024 20:38

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from b1a75a9 to a2c39db Compare January 17, 2025 22:27

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 853e5cc to 23a6ab9 Compare January 31, 2025 22:13

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 23a6ab9 to f5f875c Compare February 18, 2025 21:36

renovate bot force-pushed the renovate/major-react-router-monorepo branch from f5f875c to bf9ea34 Compare March 7, 2025 00:36

renovate bot force-pushed the renovate/major-react-router-monorepo branch from bf9ea34 to 174b2fb Compare March 19, 2025 18:24

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 174b2fb to 3f150c3 Compare March 29, 2025 00:12

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 3f150c3 to 24475cf Compare April 11, 2025 23:59

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 24475cf to 82e8237 Compare April 19, 2025 03:36

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from f73c1f2 to a77f43b Compare April 29, 2025 11:46

renovate bot force-pushed the renovate/major-react-router-monorepo branch from a77f43b to d08c081 Compare May 10, 2025 15:27

renovate bot force-pushed the renovate/major-react-router-monorepo branch from d08c081 to faeeffa Compare May 27, 2025 04:16

renovate bot force-pushed the renovate/major-react-router-monorepo branch from faeeffa to 178064d Compare June 6, 2025 16:48

renovate bot force-pushed the renovate/major-react-router-monorepo branch from 178064d to 3f6b350 Compare July 6, 2025 04:13

renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 71e6530 to c1c9470 Compare August 7, 2025 22:33

fix(deps): update dependency react-router-dom to v7

7de803d

renovate bot force-pushed the renovate/major-react-router-monorepo branch from c1c9470 to 7de803d Compare September 17, 2025 03:59

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(deps): update dependency react-router-dom to v7 #423

fix(deps): update dependency react-router-dom to v7 #423

Uh oh!

renovate bot commented Nov 5, 2021 •

edited

Loading

Uh oh!

renovate bot commented Aug 29, 2022 •

edited

Loading

Uh oh!

socket-security bot commented Aug 29, 2022 •

edited

Loading

Uh oh!

socket-security bot commented Sep 17, 2025

Uh oh!

Uh oh!

Uh oh!

fix(deps): update dependency react-router-dom to v7 #423

Are you sure you want to change the base?

fix(deps): update dependency react-router-dom to v7 #423

Uh oh!

Conversation

renovate bot commented Nov 5, 2021 • 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

Major Changes

Minor Changes

Patch Changes

v6.4.4: v6.4.4

What's Changed

v6.3.0: react-router@v6.3.0

What's Changed

New Contributors

What's Changed

🐛 Bug Fixes

New Contributors

🐛 Bug fixes

✨ Features

New Contributors

🐛 Bug fixes

✨ Features

💅 Enhancements

New Contributors

✨ Features

renovate bot commented Nov 5, 2021 •

edited

Loading

`v6.4.4`: v6.4.4

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