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/dev@7.14.0-pre.0

Minor Changes

• Add support for Vite 8 (#14876)

Patch Changes

• support for prerendering multiple server bundles with v8_viteEnvironmentApi (#14921)

• rsc framework mode prerender / spa mode support (#14907)

• UNSTABLE RSC FRAMEWORK MODE BREAKING CHANGE - Existing route module exports remain unchanged from stable v7 non-RSC mode, but new exports are added for RSC mode. If you want to use RSC features, you will need to update your route modules to export the new annotations. (#14901)

  If you are using RSC framework mode currently, you will need to update your route modules to the new conventions. The following route module components have their own mutually exclusive server component counterparts:

  Server Component Export	Client Component
  ServerComponent	default
  ServerErrorBoundary	ErrorBoundary
  ServerLayout	Layout
  ServerHydrateFallback	HydrateFallback

  If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also server components. If you want to keep those as server components, you can rename them and prefix them with Server. If you were previously importing the implementations of those components from a client module, you can simply inline them.

  Example:

  Before

  import { ErrorBoundary as ClientErrorBoundary } from "./client";
  
  export function ServerComponent() {
    // ...
  }
  
  export function ErrorBoundary() {
    return <ClientErrorBoundary />;
  }
  
  export function Layout() {
    // ...
  }
  
  export function HydrateFallback() {
    // ...
  }

  After

  export function ServerComponent() {
    // ...
  }
  
  export function ErrorBoundary() {
    // previous implementation of ClientErrorBoundary, this is now a client component
  }
  
  export function ServerLayout() {
    // rename previous Layout export to ServerLayout to make it a server component
  }
  
  export function ServerHydrateFallback() {
    // rename previous HydrateFallback export to ServerHydrateFallback to make it a server component
  }

• update the reveal command to support rsc for entry.client, entry.rsc, entry.ssr (#14904)

• Updated dependencies:

  • react-router@7.14.0-pre.0
  • @react-router/node@7.14.0-pre.0
  • @react-router/serve@7.14.0-pre.0

react-router@7.14.0-pre.0

Patch Changes

• UNSTABLE RSC FRAMEWORK MODE BREAKING CHANGE - Existing route module exports remain unchanged from stable v7 non-RSC mode, but new exports are added for RSC mode. If you want to use RSC features, you will need to update your route modules to export the new annotations. (#14901)

  If you are using RSC framework mode currently, you will need to update your route modules to the new conventions. The following route module components have their own mutually exclusive server component counterparts:

  Server Component Export	Client Component
  ServerComponent	default
  ServerErrorBoundary	ErrorBoundary
  ServerLayout	Layout
  ServerHydrateFallback	HydrateFallback

  If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also server components. If you want to keep those as server components, you can rename them and prefix them with Server. If you were previously importing the implementations of those components from a client module, you can simply inline them.

  Example:

  Before

  import { ErrorBoundary as ClientErrorBoundary } from "./client";
  
  export function ServerComponent() {
    // ...
  }
  
  export function ErrorBoundary() {
    return <ClientErrorBoundary />;
  }
  
  export function Layout() {
    // ...
  }
  
  export function HydrateFallback() {
    // ...
  }

  After

  export function ServerComponent() {
    // ...
  }
  
  export function ErrorBoundary() {
    // previous implementation of ClientErrorBoundary, this is now a client component
  }
  
  export function ServerLayout() {
    // rename previous Layout export to ServerLayout to make it a server component
  }
  
  export function ServerHydrateFallback() {
    // rename previous HydrateFallback export to ServerHydrateFallback to make it a server component
  }

• rsc Link prefetch (#14902)

• Remove recursion from turbo-stream v2 allowing for encoding / decoding of massive payloads. (#14838)

• encodeViaTurboStream leaked memory via unremoved AbortSignal listener (#14900)

@react-router/architect@7.14.0-pre.0

Patch Changes

• Updated dependencies:
  • react-router@7.14.0-pre.0
  • @react-router/node@7.14.0-pre.0

@react-router/cloudflare@7.14.0-pre.0

Patch Changes

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

react-router-dom@7.14.0-pre.0

Patch Changes

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

@react-router/express@7.14.0-pre.0

Patch Changes

• Updated dependencies:
  • react-router@7.14.0-pre.0
  • @react-router/node@7.14.0-pre.0

@react-router/fs-routes@7.14.0-pre.0

Patch Changes

• Updated dependencies:
  • @react-router/dev@7.14.0-pre.0

@react-router/node@7.14.0-pre.0

Patch Changes

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

@react-router/remix-routes-option-adapter@7.14.0-pre.0

Patch Changes

• Updated dependencies:
  • @react-router/dev@7.14.0-pre.0

@react-router/serve@7.14.0-pre.0

Patch Changes

• Updated dependencies:
  • react-router@7.14.0-pre.0
  • @react-router/node@7.14.0-pre.0
  • @react-router/express@7.14.0-pre.0

create-react-router@7.14.0-pre.0