Skip to content

chore(deps): update dependency react-router-dom to v7 #617

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update dependency react-router-dom to v7 #617

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 7, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
react-router-dom (source) ^6.14.2 -> ^6.14.2 || ^7.0.0 age confidence
react-router-dom (source) 6.30.2 -> 7.9.6 age confidence

Release Notes

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

v7.9.6

Compare Source

Patch Changes

v7.9.5

Compare Source

Patch Changes

v7.9.4

Compare Source

Patch Changes

v7.9.3

Compare Source

Patch Changes

v7.9.2

Compare Source

Patch Changes

v7.9.1

Compare Source

Patch Changes

v7.9.0

Compare Source

Patch Changes

v7.8.2

Compare Source

Patch Changes

v7.8.1

Compare Source

Patch Changes

v7.8.0

Compare Source

Patch Changes

v7.7.1

Compare Source

Patch Changes

v7.7.0

Compare Source

Patch Changes

v7.6.3

Compare Source

Patch Changes

v7.6.2

Compare Source

Patch Changes

v7.6.1

Compare Source

Patch Changes

v7.6.0

Compare Source

Patch Changes

v7.5.3

Compare Source

Patch Changes

v7.5.2

Compare Source

Patch Changes

v7.5.1

Compare Source

Patch Changes

v7.5.0

Compare Source

Patch Changes

v7.4.1

Compare Source

Patch Changes

v7.4.0

Compare Source

Patch Changes

v7.3.0

Compare Source

Patch Changes

v7.2.0

Compare Source

Patch Changes

v7.1.5

Compare Source

Patch Changes

v7.1.4

Compare Source

Patch Changes

v7.1.3

Compare Source

Patch Changes

v7.1.2

Compare Source

Patch Changes

v7.1.1

Compare Source

Patch Changes

v7.1.0

Compare Source

Patch Changes

v7.0.2

Compare Source

Patch Changes

v7.0.1

Compare Source

Patch Changes

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

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/New_York, Automerge - At any time (no schedule defined).

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

♻ 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.

@renovate
Copy link
Contributor Author

renovate bot commented Jul 7, 2025 •
edited
Loading

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @edx/[email protected]
npm error Found: [email protected]
npm error node_modules/react-router-dom
npm error   dev react-router-dom@"7.9.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react-router-dom@"^6.0.0" from @edx/[email protected]
npm error node_modules/@edx/frontend-platform
npm error   dev @edx/frontend-platform@"^8.3.1" from the root project
npm error   peer @edx/frontend-platform@"^7.0.0 || ^8.0.0" from @openedx/[email protected]
npm error   node_modules/@openedx/frontend-plugin-framework
npm error     @openedx/frontend-plugin-framework@"^1.7.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react-router-dom
npm error   peer react-router-dom@"^6.0.0" from @edx/[email protected]
npm error   node_modules/@edx/frontend-platform
npm error     dev @edx/frontend-platform@"^8.3.1" from the root project
npm error     peer @edx/frontend-platform@"^7.0.0 || ^8.0.0" from @openedx/[email protected]
npm error     node_modules/@openedx/frontend-plugin-framework
npm error       @openedx/frontend-plugin-framework@"^1.7.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-11-18T22_13_25_272Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-18T22_13_25_272Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from e8e0736 to 1336734 Compare July 14, 2025 09:56
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 3 times, most recently from 40dae2f to 3392ddc Compare July 21, 2025 17:40
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 0d51d43 to 92560bb Compare July 28, 2025 11:44
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 8f54fbe to c879f08 Compare August 7, 2025 21:11
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 505f132 to 6b2a725 Compare August 15, 2025 20:34
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from b90b0bc to 77ad00d Compare August 22, 2025 19:41
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 1e7f6a4 to 67c1ca5 Compare August 29, 2025 17:06
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 3 times, most recently from d08e8a6 to a7bcc22 Compare September 15, 2025 09:07
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from 2ee1aa0 to f15ac38 Compare September 22, 2025 09:41
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 8 times, most recently from d991855 to 38ab1a1 Compare September 29, 2025 16:45
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch from 38ab1a1 to 5bcef0e Compare October 7, 2025 17:56
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 5 times, most recently from 9ca6d2f to ecb5724 Compare October 14, 2025 16:45
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch from ecb5724 to 62fed41 Compare October 20, 2025 08:46
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 4 times, most recently from 242dd4e to 49bb872 Compare November 3, 2025 10:33
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch 2 times, most recently from d4cde32 to 061fb25 Compare November 13, 2025 23:41
@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch from 061fb25 to 1bf83c0 Compare November 17, 2025 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant