chore: Update version for release (pre)

[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.

⚠️⚠️⚠️⚠️⚠️⚠️

release-next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

react-router@6.26.0-pre.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)

Patch Changes

• Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#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-dom@6.26.0-pre.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)

Patch Changes

• Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#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-pre.0

Minor Changes

• Add a new unstable_data() API for usage with Remix Single Fetch (#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)

Patch Changes

• Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations (#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)

  • During initial hydration, router.state.matches will now include any partial matches so that we can render ancestor HydrateFallback components

react-router-dom-v5-compat@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

react-router-native@6.26.0-pre.0

Patch Changes

• Updated dependencies:
  • react-router@6.26.0-pre.0