diff --git a/.changeset/fifty-rockets-hide.md b/.changeset/fifty-rockets-hide.md deleted file mode 100644 index c765bee5fe..0000000000 --- a/.changeset/fifty-rockets-hide.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -"@remix-run/router": minor ---- - -Add a new `unstable_data()` API for usage with Remix Single Fetch - -- This API is not intended for direct usage in React Router SPA applications -- It is primarily intended for usage with `createStaticHandler.query()` to allow loaders/actions to return arbitrary data + `status`/`headers` without forcing the serialization of data into a `Response` instance -- This allows for more advanced serialization tactics via `unstable_dataStrategy` such as serializing via `turbo-stream` in Remix Single Fetch -- ⚠️ This removes the `status` field from `HandlerResult` - - If you need to return a specific `status` from `unstable_dataStrategy` you should instead do so via `unstable_data()` diff --git a/.changeset/five-bottles-press.md b/.changeset/five-bottles-press.md deleted file mode 100644 index bc5c9497c6..0000000000 --- a/.changeset/five-bottles-press.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"@remix-run/router": minor -"react-router": minor -"react-router-dom": minor ---- - -Add a new `replace(url, init?)` alternative to `redirect(url, init?)` that performs a `history.replaceState` instead of a `history.pushState` on client-side navigation redirects diff --git a/.changeset/hip-poets-provide.md b/.changeset/hip-poets-provide.md deleted file mode 100644 index 9740048a14..0000000000 --- a/.changeset/hip-poets-provide.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -"@remix-run/router": patch ---- - -Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations - -- When a `fetcher.load` is interrupted by an `action` submission, we track it internally and force revalidation once the `action` completes -- We previously only cleared out this internal tracking info on a successful _navigation_ submission -- Therefore, if the `fetcher.load` was interrupted by a `fetcher.submit`, then we wouldn't remove it from this internal tracking info on successful load (incorrectly) -- And then on the next navigation it's presence in the internal tracking would automatically trigger execution of the `fetcher.load` again, ignoring any `shouldRevalidate` logic -- This fix cleans up the internal tracking so it applies to both navigation submission and fetcher submissions diff --git a/.changeset/pre.json b/.changeset/pre.json deleted file mode 100644 index 41a39ebf49..0000000000 --- a/.changeset/pre.json +++ /dev/null @@ -1,18 +0,0 @@ -{ - "mode": "exit", - "tag": "pre", - "initialVersions": { - "react-router": "6.25.1", - "react-router-dom": "6.25.1", - "react-router-dom-v5-compat": "6.25.1", - "react-router-native": "6.25.1", - "@remix-run/router": "1.18.0" - }, - "changesets": [ - "fifty-rockets-hide", - "five-bottles-press", - "hip-poets-provide", - "sour-dryers-walk", - "tricky-frogs-hug" - ] -} diff --git a/.changeset/sour-dryers-walk.md b/.changeset/sour-dryers-walk.md deleted file mode 100644 index c1446de81c..0000000000 --- a/.changeset/sour-dryers-walk.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"react-router-dom": patch -"react-router": patch -"@remix-run/router": patch ---- - -Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` - -- During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components diff --git a/.changeset/tricky-frogs-hug.md b/.changeset/tricky-frogs-hug.md deleted file mode 100644 index e88ce66052..0000000000 --- a/.changeset/tricky-frogs-hug.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@remix-run/router": patch ---- - -[REMOVE] Export DataWithResponseInit for Remix usage diff --git a/packages/react-router-dom-v5-compat/CHANGELOG.md b/packages/react-router-dom-v5-compat/CHANGELOG.md index 601875c238..51677f954e 100644 --- a/packages/react-router-dom-v5-compat/CHANGELOG.md +++ b/packages/react-router-dom-v5-compat/CHANGELOG.md @@ -1,22 +1,13 @@ # `react-router-dom-v5-compat` -## 6.26.0-pre.1 +## 6.26.0 ### Patch Changes - Updated dependencies: - - `@remix-run/router@1.19.0-pre.1` - - `react-router@6.26.0-pre.1` - - `react-router-dom@6.26.0-pre.1` - -## 6.26.0-pre.0 - -### Patch Changes - -- Updated dependencies: - - `@remix-run/router@1.19.0-pre.0` - - `react-router@6.26.0-pre.0` - - `react-router-dom@6.26.0-pre.0` + - `@remix-run/router@1.19.0` + - `react-router@6.26.0` + - `react-router-dom@6.26.0` ## 6.25.1 diff --git a/packages/react-router-dom-v5-compat/package.json b/packages/react-router-dom-v5-compat/package.json index 75d131a706..5bb981bb10 100644 --- a/packages/react-router-dom-v5-compat/package.json +++ b/packages/react-router-dom-v5-compat/package.json @@ -1,6 +1,6 @@ { "name": "react-router-dom-v5-compat", - "version": "6.26.0-pre.1", + "version": "6.26.0", "description": "Migration path to React Router v6 from v4/5", "keywords": [ "react", diff --git a/packages/react-router-dom/CHANGELOG.md b/packages/react-router-dom/CHANGELOG.md index 51b9605b15..152d358a9b 100644 --- a/packages/react-router-dom/CHANGELOG.md +++ b/packages/react-router-dom/CHANGELOG.md @@ -1,14 +1,6 @@ # `react-router-dom` -## 6.26.0-pre.1 - -### Patch Changes - -- Updated dependencies: - - `@remix-run/router@1.19.0-pre.1` - - `react-router@6.26.0-pre.1` - -## 6.26.0-pre.0 +## 6.26.0 ### Minor Changes @@ -17,12 +9,10 @@ ### Patch Changes - Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` ([#11838](https://github.com/remix-run/react-router/pull/11838)) - - During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components - - Updated dependencies: - - `@remix-run/router@1.19.0-pre.0` - - `react-router@6.26.0-pre.0` + - `@remix-run/router@1.19.0` + - `react-router@6.26.0` ## 6.25.1 @@ -37,7 +27,6 @@ ### Minor Changes - Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://github.com/remix-run/react-router/pull/11769)) - - When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a `Response` with a `4xx`/`5xx` status code - You may still opt-into revalidation via `shouldRevalidate` - This also changes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus` @@ -64,7 +53,6 @@ ### Minor Changes - Add support for Lazy Route Discovery (a.k.a. Fog of War) ([#11626](https://github.com/remix-run/react-router/pull/11626)) - - RFC: - `unstable_patchRoutesOnMiss` docs: diff --git a/packages/react-router-dom/package.json b/packages/react-router-dom/package.json index bb08a82576..54ed162217 100644 --- a/packages/react-router-dom/package.json +++ b/packages/react-router-dom/package.json @@ -1,6 +1,6 @@ { "name": "react-router-dom", - "version": "6.26.0-pre.1", + "version": "6.26.0", "description": "Declarative routing for React web applications", "keywords": [ "react", diff --git a/packages/react-router-native/CHANGELOG.md b/packages/react-router-native/CHANGELOG.md index 6ab13153fc..7f7b3d6108 100644 --- a/packages/react-router-native/CHANGELOG.md +++ b/packages/react-router-native/CHANGELOG.md @@ -1,18 +1,11 @@ # `react-router-native` -## 6.26.0-pre.1 +## 6.26.0 ### Patch Changes - Updated dependencies: - - `react-router@6.26.0-pre.1` - -## 6.26.0-pre.0 - -### Patch Changes - -- Updated dependencies: - - `react-router@6.26.0-pre.0` + - `react-router@6.26.0` ## 6.25.1 diff --git a/packages/react-router-native/package.json b/packages/react-router-native/package.json index f1714a9bea..c6833d0c15 100644 --- a/packages/react-router-native/package.json +++ b/packages/react-router-native/package.json @@ -1,6 +1,6 @@ { "name": "react-router-native", - "version": "6.26.0-pre.1", + "version": "6.26.0", "description": "Declarative routing for React Native applications", "keywords": [ "react", diff --git a/packages/react-router/CHANGELOG.md b/packages/react-router/CHANGELOG.md index 1e379d0353..083bdb9b16 100644 --- a/packages/react-router/CHANGELOG.md +++ b/packages/react-router/CHANGELOG.md @@ -1,13 +1,6 @@ # `react-router` -## 6.26.0-pre.1 - -### Patch Changes - -- Updated dependencies: - - `@remix-run/router@1.19.0-pre.1` - -## 6.26.0-pre.0 +## 6.26.0 ### Minor Changes @@ -16,11 +9,9 @@ ### Patch Changes - Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` ([#11838](https://github.com/remix-run/react-router/pull/11838)) - - During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components - - Updated dependencies: - - `@remix-run/router@1.19.0-pre.0` + - `@remix-run/router@1.19.0` ## 6.25.1 @@ -31,7 +22,6 @@ No significant changes to this package were made in this release. [See the repo ### Minor Changes - Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://github.com/remix-run/react-router/pull/11769)) - - When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a `Response` with a `4xx`/`5xx` status code - You may still opt-into revalidation via `shouldRevalidate` - This also changes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus` @@ -55,7 +45,6 @@ No significant changes to this package were made in this release. [See the repo ### Minor Changes - Add support for Lazy Route Discovery (a.k.a. Fog of War) ([#11626](https://github.com/remix-run/react-router/pull/11626)) - - RFC: - `unstable_patchRoutesOnMiss` docs: diff --git a/packages/react-router/package.json b/packages/react-router/package.json index 421dc5aa46..be90f5b3e5 100644 --- a/packages/react-router/package.json +++ b/packages/react-router/package.json @@ -1,6 +1,6 @@ { "name": "react-router", - "version": "6.26.0-pre.1", + "version": "6.26.0", "description": "Declarative routing for React", "keywords": [ "react", diff --git a/packages/router/CHANGELOG.md b/packages/router/CHANGELOG.md index 99962cb216..d250f4ab2d 100644 --- a/packages/router/CHANGELOG.md +++ b/packages/router/CHANGELOG.md @@ -1,37 +1,26 @@ # `@remix-run/router` -## 1.19.0-pre.1 - -### Patch Changes - -- [REMOVE] Export DataWithResponseInit for Remix usage ([#11859](https://github.com/remix-run/react-router/pull/11859)) - -## 1.19.0-pre.0 +## 1.19.0 ### Minor Changes +- Add a new `replace(url, init?)` alternative to `redirect(url, init?)` that performs a `history.replaceState` instead of a `history.pushState` on client-side navigation redirects ([#11811](https://github.com/remix-run/react-router/pull/11811)) - Add a new `unstable_data()` API for usage with Remix Single Fetch ([#11836](https://github.com/remix-run/react-router/pull/11836)) - - This API is not intended for direct usage in React Router SPA applications - It is primarily intended for usage with `createStaticHandler.query()` to allow loaders/actions to return arbitrary data + `status`/`headers` without forcing the serialization of data into a `Response` instance - This allows for more advanced serialization tactics via `unstable_dataStrategy` such as serializing via `turbo-stream` in Remix Single Fetch - ⚠️ This removes the `status` field from `HandlerResult` - If you need to return a specific `status` from `unstable_dataStrategy` you should instead do so via `unstable_data()` -- Add a new `replace(url, init?)` alternative to `redirect(url, init?)` that performs a `history.replaceState` instead of a `history.pushState` on client-side navigation redirects ([#11811](https://github.com/remix-run/react-router/pull/11811)) - ### Patch Changes - Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations ([#11839](https://github.com/remix-run/react-router/pull/11839)) - - When a `fetcher.load` is interrupted by an `action` submission, we track it internally and force revalidation once the `action` completes - We previously only cleared out this internal tracking info on a successful _navigation_ submission - Therefore, if the `fetcher.load` was interrupted by a `fetcher.submit`, then we wouldn't remove it from this internal tracking info on successful load (incorrectly) - And then on the next navigation it's presence in the internal tracking would automatically trigger execution of the `fetcher.load` again, ignoring any `shouldRevalidate` logic - This fix cleans up the internal tracking so it applies to both navigation submission and fetcher submissions - - Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` ([#11838](https://github.com/remix-run/react-router/pull/11838)) - - During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components ## 1.18.0 @@ -39,7 +28,6 @@ ### Minor Changes - Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://github.com/remix-run/react-router/pull/11769)) - - When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a `Response` with a `4xx`/`5xx` status code - You may still opt-into revalidation via `shouldRevalidate` - This also changes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus` diff --git a/packages/router/package.json b/packages/router/package.json index 9b49ee9350..2369d2ade1 100644 --- a/packages/router/package.json +++ b/packages/router/package.json @@ -1,6 +1,6 @@ { "name": "@remix-run/router", - "version": "1.19.0-pre.1", + "version": "1.19.0", "description": "Nested/Data-driven/Framework-agnostic Routing", "keywords": [ "remix",