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@7.5.1-pre.0

Patch Changes

• Fix single fetch bug where no revalidation request would be made when navigating upwards to a reused parent route (#13253)

• When using the object-based route.lazy API, the HydrateFallback and hydrateFallbackElement properties are now skipped when lazy loading routes after hydration. (#13376)

  If you move the code for these properties into a separate file, you can use this optimization to avoid downloading unused hydration code. For example:

  createBrowserRouter([ { path: "/show/:showId", lazy: { loader: async () => (await import("./show.loader.js")).loader, Component: async () => (await import("./show.component.js")).Component, HydrateFallback: async () => (await import("./show.hydrate-fallback.js")).HydrateFallback, }, }, ]);

• Properly revalidate prerendered paths when param values change (#13380)

• UNSTABLE: Add a new unstable_runClientMiddleware argument to dataStrategy to enable middleware execution in custom dataStrategy implementations (#13395)

• UNSTABLE: Add better error messaging when getLoadContext is not updated to return a Map" (#13242)

• Do not automatically add null to staticHandler.query() context.loaderData if routes do not have loaders (#13223)

  • This was a Remix v2 implementation detail inadvertently left in for React Router v7
  • Now that we allow returning undefined from loaders, our prior check of loaderData[routeId] !== undefined was no longer sufficient and was changed to a routeId in loaderData check - these null values can cause issues for this new check
  • ⚠️ This could be a "breaking bug fix" for you if you are doing manual SSR with createStaticHandler()/<StaticRouterProvider>, and using context.loaderData to control <RouterProvider> hydration behavior on the client

• Fix prerendering when a loader returns a redirect (#13365)

• UNSTABLE: Update context type for LoaderFunctionArgs/ActionFunctionArgs when middleware is enabled (#13381)

• Add support for the new unstable_shouldCallHandler/unstable_shouldRevalidateArgs APIs in dataStrategy (#13253)

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

Patch Changes

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

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

Patch Changes

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

@react-router/dev@7.5.1-pre.0

Patch Changes

• Fix prerendering when a loader returns a redirect (#13365)
• Updated dependencies:
  • react-router@7.5.1-pre.0
  • @react-router/node@7.5.1-pre.0
  • @react-router/serve@7.5.1-pre.0

react-router-dom@7.5.1-pre.0

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

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

Patch Changes

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

create-react-router@7.5.1-pre.0