Skip to content

chore(deps): update react-router to v8.4.0 - #744

Merged
nedtwigg merged 1 commit into
mainfrom
renovate/react-router
Sep 22, 2026
Merged

nedtwigg merged 1 commit into
mainfrom
renovate/react-router

Conversation

@renovate

@renovate renovate Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@react-router/dev (source) 8.3.18.4.0 age adoption passing confidence
react-router (source) 8.3.18.4.0 age adoption passing confidence

Release Notes

remix-run/react-router (@​react-router/dev)

v8.4.0

Compare Source

Patch Changes
  • Fix action submissions behind an HTTPS reverse proxy in react-router dev and vite preview by using X-Forwarded-Proto when constructing request.url (#​15466)
    • No React Router configuration is required
    • The URL host continues to come from Host, not X-Forwarded-Host
    • Configure reverse proxies to overwrite client-supplied X-Forwarded-Proto headers
    • Do not expose dev or preview servers publicly
  • Pass development conditions as CLI flags when relaunching the dev process (#​15435)
  • Fix stack trace locations for split route modules when source maps are enabled in the reactRouter Vite plugin (#​15440)
  • Updated dependencies:
remix-run/react-router (react-router)

v8.4.0

Compare Source

Minor Changes
  • Deprecate the createStaticRouter({ branches }) option (#​15297)
    • createStaticRouter now caches route branches internally, ignores branches, and logs a deprecation warning when the option is provided
    • The deprecated EntryContext.branches property remains available for compatibility but is always an empty array
Patch Changes
  • Prevent stale route discovery during manifest version-mismatch recovery (#​15489)
    • Keep concurrent manifest responses pending while a document reload is in progress
    • Report a discovery error when a previous reload failed to resolve a version mismatch instead of loading a stale route or reloading repeatedly
    • Fail pending requests if a document reload does not complete within five seconds or the document is restored from the back-forward cache, allowing subsequent requests to recover
  • Preserve lazy route module import errors during SPA navigations instead of replacing them with a missing dataStrategy result error (#​15464)
  • Switch to more granular internal router contexts to avoid unnecessary route component re-renders when unrelated data router state changes (#​15376)
    • ⚠️ This contains some breaking changes to exported UNSAFE_ contexts, so please review carefully if you are using those unsafe exports
  • Correctly escape streamed RSC redirect locations in meta tag attributes (#​15491)
  • Avoid unintended document.startViewTransition calls during initial hydration and router.revalidate() calls (#​15484)
  • Fix SingleFetchNoResultError thrown when a fetcher revalidates against a splat route during lazy route discovery (#​15395)
    • Track discovery per fetcher load so revalidation waits for the current load's discovery, even when the fetcher key is reused, while still restarting interrupted loaders after discovery completes
  • Preserve the underlying decode failure as the cause of the Unable to decode turbo-stream response error (#​15450)
Unstable Changes

⚠️ Unstable features are not recommended for production use

  • Add a Data Mode future.unstable_routePatternMatching flag for more efficient route matching powered by @remix-run/route-pattern (#​15298)
    • Add an unstable_validateParams route field to reject invalid parameter values and continue matching
  • Document access control requirements for RSC Server Functions (#​15490)
    • Treat every Server Function as a public endpoint that must perform all of its own access control checks
    • Recommend route actions when access control should be provided by route middleware

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • Only on Monday (* * * * 1)
  • 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.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying mouseterm with  Cloudflare Pages  Cloudflare Pages

Latest commit: b562c27
Status: ✅  Deploy successful!
Preview URL: https://407c6a72.mouseterm.pages.dev
Branch Preview URL: https://renovate-react-router.mouseterm.pages.dev

View logs

@nedtwigg
nedtwigg marked this pull request as ready for review September 22, 2026 18:04
@nedtwigg
nedtwigg merged commit 3b7f381 into main Sep 22, 2026
12 checks passed
@renovate
renovate Bot deleted the renovate/react-router branch September 22, 2026 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant