chore: Update version for release

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

Releases

[email protected]

Patch Changes

• • Update client-side router to run client middleware on initial load even if no loaders exist (#14348)
  • Update createRoutesStub to run route middleware
    • You will need to set the <RoutesStub future={{ v8_middleware: true }} /> flag to enable the proper context type

• Update Lazy Route Discovery manifest requests to use a singular comma-separated paths query param instead of repeated p query params (#14321)

  • This is because Cloudflare has a hard limit of 100 URL search param key/value pairs when used as a key for caching purposes
  • If more that 100 paths were included, the cache key would be incomplete and could produce false-positive cache hits

• [UNSTABLE] Add fetcher.unstable_reset() API (#14206)

• Made useOutlet element reference have stable identity in-between route chages (#13382)

• feat: enable full transition support for the rsc router (#14362)

• In RSC Data Mode, handle SSR'd client errors and re-try in the browser (#14342)

• Support middleware prop on <Route> for usage with a data router via createRoutesFromElements (#14357)

• Handle encoded question mark and hash characters in ancestor splat routes (#14249)

• Fail gracefully on manifest version mismatch logic if sessionStorage access is blocked (#14335)

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • [email protected]

@react-router/[email protected]

Patch Changes

• Fix preset future flags being ignored during config resolution (#14369)

  Fixes a bug where future flags defined by presets were completely ignored. The config resolution was incorrectly reading from reactRouterUserConfig.future instead of the merged userAndPresetConfigs.future, causing all preset-defined future flags to be lost.

  This fix ensures presets can properly enable experimental features as intended by the preset system design.

• Add unstable support for RSC Framework Mode (#14336)

• Switch internal vite plugin Response logic to use @remix-run/node-fetch-server (#13927)

• Updated dependencies:

  • [email protected]
  • @react-router/[email protected]
  • @react-router/[email protected]

[email protected]

Patch Changes

• Updated dependencies:
  • [email protected]

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • @react-router/[email protected]

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • [email protected]

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • @react-router/[email protected]

@react-router/[email protected]

Patch Changes

• disable compression for RSC responses for now (#14381)
• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]
  • @react-router/[email protected]

[email protected]