chore: Update version for release

CHANGELOG.md

@@ -202,7 +202,7 @@ With this flag enabled, `action`'s that return/throw a `4xx`/`5xx` response stat
 
 ### Minor Changes
 
-- Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098), ([#11377](https://github.com/remix-run/react-router/pull/11377)))
+- Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098), [#11377](https://github.com/remix-run/react-router/pull/11377))
 - `@remix-run/router` - Add a new `future.unstable_skipActionRevalidation` future flag ([#11098](https://github.com/remix-run/react-router/pull/11098))
 - `@remix-run/router` - SSR: Added a new `skipLoaderErrorBubbling` options to the `staticHandler.query` method to disable error bubbling by the static handler for use in Remix's Single Fetch implementation ([#11098](https://github.com/remix-run/react-router/pull/11098), ([#11377](https://github.com/remix-run/react-router/pull/11377)))
 

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

@@ -1,29 +1,19 @@
 # `react-router-dom-v5-compat`
 
-## 6.23.0-pre.1
-
-### Patch Changes
-
-- Updated dependencies:
-  - `@remix-run/[email protected]`
-  - `[email protected]`
-  - `[email protected]`
-
-## 6.23.0-pre.0
+## 6.23.0
 
 ### Minor Changes
 
 - Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - This option allows Data Router applications to take control over the approach for executing route loaders and actions
   - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more
 
 ### Patch Changes
 
 - Updated dependencies:
-  - `@remix-run/[email protected]-pre.0`
-  - `[email protected]-pre.0`
-  - `[email protected]-pre.0`
+  - `@remix-run/[email protected]`
+  - `[email protected]`
+  - `[email protected]`
 
 ## 6.22.3
 

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

@@ -1,6 +1,6 @@
 {
   "name": "react-router-dom-v5-compat",
-  "version": "6.23.0-pre.1",
+  "version": "6.23.0",
   "description": "Migration path to React Router v6 from v4/5",
   "keywords": [
     "react",

packages/react-router-dom/CHANGELOG.md

@@ -1,27 +1,18 @@
 # `react-router-dom`
 
-## 6.23.0-pre.1
-
-### Patch Changes
-
-- Updated dependencies:
-  - `@remix-run/[email protected]`
-  - `[email protected]`
-
-## 6.23.0-pre.0
+## 6.23.0
 
 ### Minor Changes
 
 - Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - This option allows Data Router applications to take control over the approach for executing route loaders and actions
   - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more
 
 ### Patch Changes
 
 - Updated dependencies:
-  - `@remix-run/[email protected]-pre.0`
-  - `[email protected]-pre.0`
+  - `@remix-run/[email protected]`
+  - `[email protected]`
 
 ## 6.22.3
 

packages/react-router-dom/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-router-dom",
-  "version": "6.23.0-pre.1",
+  "version": "6.23.0",
   "description": "Declarative routing for React web applications",
   "keywords": [
     "react",

packages/react-router-native/CHANGELOG.md

@@ -1,25 +1,17 @@
 # `react-router-native`
 
-## 6.23.0-pre.1
-
-### Patch Changes
-
-- Updated dependencies:
-  - `[email protected]`
-
-## 6.23.0-pre.0
+## 6.23.0
 
 ### Minor Changes
 
 - Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - This option allows Data Router applications to take control over the approach for executing route loaders and actions
   - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more
 
 ### Patch Changes
 
 - Updated dependencies:
-  - `[email protected]-pre.0`
+  - `[email protected]`
 
 ## 6.22.3
 

packages/react-router-native/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-router-native",
-  "version": "6.23.0-pre.1",
+  "version": "6.23.0",
   "description": "Declarative routing for React Native applications",
   "keywords": [
     "react",

packages/react-router/CHANGELOG.md

@@ -1,25 +1,17 @@
 # `react-router`
 
-## 6.23.0-pre.1
-
-### Patch Changes
-
-- Updated dependencies:
-  - `@remix-run/[email protected]`
-
-## 6.23.0-pre.0
+## 6.23.0
 
 ### Minor Changes
 
 - Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - This option allows Data Router applications to take control over the approach for executing route loaders and actions
   - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more
 
 ### Patch Changes
 
 - Updated dependencies:
-  - `@remix-run/[email protected]-pre.0`
+  - `@remix-run/[email protected]`
 
 ## 6.22.3
 

packages/react-router/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-router",
-  "version": "6.23.0-pre.1",
+  "version": "6.23.0",
   "description": "Declarative routing for React",
   "keywords": [
     "react",

packages/router/CHANGELOG.md

@@ -1,34 +1,20 @@
 # `@remix-run/router`
 
-## 1.16.0-pre.1
-
-### Patch Changes
-
-- [REMOVE] Remove staticHandler.query flags that we can implement in dataStrategy ([#11384](https://github.com/remix-run/react-router/pull/11384))
-
-## 1.16.0-pre.0
+## 1.16.0
 
 ### Minor Changes
 
 - Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - This option allows Data Router applications to take control over the approach for executing route loaders and actions
   - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more
-
+- Move `unstable_dataStrategy` from `createStaticHandler` to `staticHandler.query` so it can be request-specific for use with the `ResponseStub` approach in Remix. It's not really applicable to `queryRoute` for now since that's a singular handler call anyway so any pre-processing/post/processing could be done there manually. ([#11377](https://github.com/remix-run/react-router/pull/11377))
 - Add a new `future.unstable_skipActionRevalidation` future flag ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
   - Currently, active loaders revalidate after any action, regardless of the result
   - With this flag enabled, actions that return/throw a 4xx/5xx response status will no longer automatically revalidate
   - This should reduce load on your server since it's rare that a 4xx/5xx should actually mutate any data
   - If you need to revalidate after a 4xx/5xx result with this flag enabled, you can still do that via returning `true` from `shouldRevalidate`
   - `shouldRevalidate` now also receives a new `unstable_actionStatus` argument alongside `actionResult` so you can make decision based on the status of the `action` response without having to encode it into the action data
-
-- - Move `unstable_dataStrategy` from `createStaticHandler` to `staticHandler.query` so it can be request-specific for use with the `ResponseStub` approach in Remix. It's not really applicable to `queryRoute` for now since that's a singular handler call anyway so any pre-processing/post/processing could be done there manually. ([#11377](https://github.com/remix-run/react-router/pull/11377))
-  - Added a new `skipLoaders` flag to `staticHandler.query` for calling only the action in Remix Single Fetch
-- Added 2 new options to the `staticHandler.query` method for use in Remix's Single Fetch implementation: ([#11098](https://github.com/remix-run/react-router/pull/11098))
-
-  - `loadRouteIds`: An optional array of route IDs to load if you wish to load a subset of the matched routes (useful for fine-grained revalidation)
-  - `skipLoaderErrorBubbling`: Disable error bubbling on loader executions for single-fetch scenarios where the client-side router will handle the bubbling
+- Added a `skipLoaderErrorBubbling` flag to `staticHandler.query` to disable error bubbling on loader executions for single-fetch scenarios where the client-side router will handle the bubbling ([#11098](https://github.com/remix-run/react-router/pull/11098))
 
 ## 1.15.3
 

packages/router/package.json

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