chore: Update version for release (#10414)

packages/react-router-dom-v5-compat/CHANGELOG.md

@@ -1,28 +1,12 @@
 # `react-router-dom-v5-compat`
 
-## 6.11.0-pre.2
+## 6.11.0
 
 ### Patch Changes
 
 - Updated dependencies:
-  - `react-router@6.11.0-pre.2`
-  - `react-router-dom@6.11.0-pre.2`
-
-## 6.11.0-pre.1
-
-### Patch Changes
-
-- Updated dependencies:
-  - `react-router-dom@6.11.0-pre.1`
-  - `react-router@6.11.0-pre.1`
-
-## 6.11.0-pre.0
-
-### Patch Changes
-
-- Updated dependencies:
-  - `react-router@6.11.0-pre.0`
-  - `react-router-dom@6.11.0-pre.0`
+  - `react-router@6.11.0`
+  - `react-router-dom@6.11.0`
 
 ## 6.10.0
 

packages/react-router-dom-v5-compat/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-router-dom-v5-compat",
-  "version": "6.11.0-pre.2",
+  "version": "6.11.0",
   "description": "Migration path to React Router v6 from v4/5",
   "keywords": [
     "react",
@@ -24,7 +24,7 @@
   "types": "./dist/index.d.ts",
   "dependencies": {
     "history": "^5.3.0",
-    "react-router": "6.11.0-pre.2"
+    "react-router": "6.11.0"
   },
   "peerDependencies": {
     "react": ">=16.8",

packages/react-router-dom/CHANGELOG.md

@@ -1,42 +1,22 @@
 # `react-router-dom`
 
-## 6.11.0-pre.2
-
-### Patch Changes
-
-- Updated dependencies:
-  - `react-router@6.11.0-pre.2`
-
-## 6.11.0-pre.1
-
-### Patch Changes
-
-- Add static prop to `StaticRouterProvider`'s internal `Router` component ([#10401](https://github.com/remix-run/react-router/pull/10401))
-- Updated dependencies:
-  - `react-router@6.11.0-pre.1`
-
-## 6.11.0-pre.0
+## 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](https://github.com/remix-run/react-router/pull/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
+- Enable `basename` support in `useFetcher` ([#10336](https://github.com/remix-run/react-router/pull/10336))
+  - If you were previously working around this issue by manually prepending the `basename` then you will need to remove the manually prepended `basename` from your `fetcher` calls (`fetcher.load('/basename/route') -> fetcher.load('/route')`)
 
 ### Patch Changes
 
 - Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/10287))
 - Fail gracefully on `<Link to="//">` and other invalid URL values ([#10367](https://github.com/remix-run/react-router/pull/10367))
-- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81) where router state updates got propagated _before_ other normal `useState` updates, which could lead to footguns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377))
+- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81) where router state updates got propagated _before_ other normal `useState` updates, which could lead to footguns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377), [#10409](https://github.com/remix-run/react-router/pull/10409))
+- Add static prop to `StaticRouterProvider`'s internal `Router` component ([#10401](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/10336))
 - Updated dependencies:
-  - `react-router@6.11.0-pre.0`
-  - `@remix-run/router@1.6.0-pre.0`
+  - `react-router@6.11.0`
+  - `@remix-run/router@1.6.0`
 
 ## 6.10.0
 

packages/react-router-dom/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-router-dom",
-  "version": "6.11.0-pre.2",
+  "version": "6.11.0",
   "description": "Declarative routing for React web applications",
   "keywords": [
     "react",
@@ -23,8 +23,8 @@
   "module": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "dependencies": {
-    "@remix-run/router": "1.6.0-pre.0",
-    "react-router": "6.11.0-pre.2"
+    "@remix-run/router": "1.6.0",
+    "react-router": "6.11.0"
   },
   "devDependencies": {
     "react": "^18.2.0",

packages/react-router-native/CHANGELOG.md

@@ -1,25 +1,11 @@
 # `react-router-native`
 
-## 6.11.0-pre.2
+## 6.11.0
 
 ### Patch Changes
 
 - Updated dependencies:
-  - `react-router@6.11.0-pre.2`
-
-## 6.11.0-pre.1
-
-### Patch Changes
-
-- Updated dependencies:
-  - `react-router@6.11.0-pre.1`
-
-## 6.11.0-pre.0
-
-### Patch Changes
-
-- Updated dependencies:
-  - `react-router@6.11.0-pre.0`
+  - `react-router@6.11.0`
 
 ## 6.10.0
 

packages/react-router-native/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-router-native",
-  "version": "6.11.0-pre.2",
+  "version": "6.11.0",
   "description": "Declarative routing for React Native applications",
   "keywords": [
     "react",
@@ -22,7 +22,7 @@
   "types": "./dist/index.d.ts",
   "dependencies": {
     "@ungap/url-search-params": "^0.1.4",
-    "react-router": "6.11.0-pre.2"
+    "react-router": "6.11.0"
   },
   "devDependencies": {
     "react": "^18.2.0",

packages/react-router/CHANGELOG.md

@@ -1,26 +1,19 @@
 # `react-router`
 
-## 6.11.0-pre.2
-
-### Patch Changes
-
-- Avoid uneccesary unsubscribe/resubscribes on router state changes ([#10409](https://github.com/remix-run/react-router/pull/10409))
-
-## 6.11.0-pre.1
-
-## 6.11.0-pre.0
+## 6.11.0
 
 ### Patch Changes
 
 - Log loader/action errors to the console in dev for easier stack trace evaluation ([#10286](https://github.com/remix-run/react-router/pull/10286))
 - Fix bug preventing rendering of descendant `<Routes>` when `RouterProvider` errors existed ([#10374](https://github.com/remix-run/react-router/pull/10374))
 - Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/10394))
-- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81) where router state updates got propagated _before_ other normal `useState` updates, which could lead to footguns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377))
+- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81) where router state updates got propagated _before_ other normal `useState` updates, which could lead to footguns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377), [#10409](https://github.com/remix-run/react-router/pull/10409))
 - Allow `useRevalidator()` to resolve a loader-driven error boundary scenario ([#10369](https://github.com/remix-run/react-router/pull/10369))
+- Avoid unnecessary unsubscribe/resubscribes on router state changes ([#10409](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/10336))
 - Updated dependencies:
-  - `@remix-run/router@1.6.0-pre.0`
+  - `@remix-run/router@1.6.0`
 
 ## 6.10.0
 

packages/react-router/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-router",
-  "version": "6.11.0-pre.2",
+  "version": "6.11.0",
   "description": "Declarative routing for React",
   "keywords": [
     "react",
@@ -23,7 +23,7 @@
   "module": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "dependencies": {
-    "@remix-run/router": "1.6.0-pre.0"
+    "@remix-run/router": "1.6.0"
   },
   "devDependencies": {
     "react": "^18.2.0"

packages/router/CHANGELOG.md

@@ -1,17 +1,18 @@
 # `@remix-run/router`
 
-## 1.6.0-pre.0
+## 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](https://github.com/remix-run/react-router/pull/10336))
+- Enable relative routing in the `@remix-run/router` when providing a source route ID from which the path is relative to: ([#10336](https://github.com/remix-run/react-router/pull/10336))
 
-    - Example: `router.navigate("../path", { fromRouteId: "some-route" })`.
-    - This also applies to `router.fetch` which already receives a source route ID
+  - 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
+- 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
 

packages/router/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/router",
-  "version": "1.6.0-pre.0",
+  "version": "1.6.0",
   "description": "Nested/Data-driven/Framework-agnostic Routing",
   "keywords": [
     "remix",