chore: Update version for release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

Releases

react-router-dom@6.11.0

Minor Changes

• • Enable relative routing in the @remix-run/router when providing a source route ID from which the path is relative to: (#10336)

    • Example: router.navigate("../path", { fromRouteId: "some-route" }).
    • This also applies to router.fetch which already receives a source route ID

  • Introduce a new @remix-run/router future.v7_prependBasename flag to enable basename prefixing to all paths coming into router.navigate and router.fetch.

    • Previously the basename was prepended in the React Router layer, but now that relative routing is being handled by the router we need prepend the basename after resolving any relative paths
    • This also enables basename support in useFetcher as well

Patch Changes

• Fix inadvertent re-renders when using Component instead of element on a route definition (#10287)
• Fail gracefully on <Link to="//"> and other invalid URL values (#10367)
• Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#10377)
• Add static prop to StaticRouterProvider's internal Router component (#10401)
• When using a RouterProvider, useNavigate/useSubmit/fetcher.submit are now stable across location changes, since we can handle relative routing via the @remix-run/router instance and get rid of our dependence on useLocation(). When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation(). (#10336)
• Updated dependencies:
  • react-router@6.11.0
  • @remix-run/router@1.6.0

@remix-run/router@1.6.0

Minor Changes

• • Enable relative routing in the @remix-run/router when providing a source route ID from which the path is relative to: (#10336)

    • Example: router.navigate("../path", { fromRouteId: "some-route" }).
    • This also applies to router.fetch which already receives a source route ID

  • Introduce a new @remix-run/router future.v7_prependBasename flag to enable basename prefixing to all paths coming into router.navigate and router.fetch.

    • Previously the basename was prepended in the React Router layer, but now that relative routing is being handled by the router we need prepend the basename after resolving any relative paths
    • This also enables basename support in useFetcher as well

Patch Changes

• Enhance LoaderFunction/ActionFunction return type to prevent undefined from being a valid return value (#10267)
• Ensure proper 404 error on fetcher.load call to a route without a loader (#10345)
• Deprecate the createRouter detectErrorBoundary option in favor of the new mapRouteProperties option for converting a framework-agnostic route to a framework-aware route. This allows us to set more than just the hasErrorBoundary property during route pre-processing, and is now used for mapping Component -> element and ErrorBoundary -> errorElement in react-router. (#10287)
• Fixed a bug where fetchers were incorrectly attempting to revalidate on search params changes or routing to the same URL (using the same logic for route loader revalidations). However, since fetchers have a static href, they should only revalidate on action submissions or router.revalidate calls. (#10344)
• Decouple AbortController usage between revalidating fetchers and the thing that triggered them such that the unmount/deletion of a revalidating fetcher doesn't impact the ongoing triggering navigation/revalidation (#10271)

react-router@6.11.0

Patch Changes

• Log loader/action errors to the console in dev for easier stack trace evaluation (#10286)
• Fix bug preventing rendering of descendant <Routes> when RouterProvider errors existed (#10374)
• Fix inadvertent re-renders when using Component instead of element on a route definition (#10287)
• Fix detection of useNavigate in the render cycle by setting the activeRef in a layout effect, allowing the navigate function to be passed to child components and called in a useEffect there. (#10394)
• Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#10377)
• Allow useRevalidator() to resolve a loader-driven error boundary scenario (#10369)
• Avoid uneccesary unsubscribe/resubscribes on router state changes (#10409)
• When using a RouterProvider, useNavigate/useSubmit/fetcher.submit are now stable across location changes, since we can handle relative routing via the @remix-run/router instance and get rid of our dependence on useLocation(). When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation(). (#10336)
• Updated dependencies:
  • @remix-run/router@1.6.0

react-router-dom-v5-compat@6.11.0

Patch Changes

• Updated dependencies:
  • react-router@6.11.0
  • react-router-dom@6.11.0

react-router-native@6.11.0

Patch Changes

• Updated dependencies:
  • react-router@6.11.0