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.2.0-pre.2

Patch Changes

• Properly handle revalidations to across a prerender/SPA boundary (#13021)

  • In "hybrid" applications where some routes are pre-rendered and some are served from a SPA fallback, we need to avoid making .data requests if the path wasn't pre-rendered because the request will 404
  • We don't know all the pre-rendered paths client-side, however:
    • All loader data in ssr:false mode is static because it's generated at build time
    • A route must use a clientLoader to do anything dynamic
    • Therefore, if a route only has a loader and not a clientLoader, we disable revalidation by default because there is no new data to retrieve
    • We short circuit and skip single fetch .data request logic if there are no server loaders with shouldLoad=true in our single fetch dataStrategy
    • This ensures that the route doesn't cause a .data request that would 404 after a submission

• Error at build time in ssr:false + prerender apps for the edge case scenario of: (#13021)

  • A parent route has only a loader (does not have a clientLoader)
  • The parent route is pre-rendered
  • The parent route has children routes which are not prerendered
  • This means that when the child paths are loaded via the SPA fallback, the parent won't have any loaderData because there is no server on which to run the loader
  • This can be resolved by either adding a parent clientLoader or pre-rendering the child paths
  • If you add a clientLoader, calling the serverLoader() on non-prerendered paths will throw a 404

@react-router/architect@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • react-router@7.2.0-pre.2
  • @react-router/node@7.2.0-pre.2

@react-router/cloudflare@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • react-router@7.2.0-pre.2

@react-router/dev@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • react-router@7.2.0-pre.2
  • @react-router/node@7.2.0-pre.2
  • @react-router/serve@7.2.0-pre.2

react-router-dom@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • react-router@7.2.0-pre.2

@react-router/express@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • react-router@7.2.0-pre.2
  • @react-router/node@7.2.0-pre.2

@react-router/fs-routes@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • @react-router/dev@7.2.0-pre.2

@react-router/node@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • react-router@7.2.0-pre.2

@react-router/remix-routes-option-adapter@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • @react-router/dev@7.2.0-pre.2

@react-router/serve@7.2.0-pre.2

Patch Changes

• Updated dependencies:
  • react-router@7.2.0-pre.2
  • @react-router/node@7.2.0-pre.2
  • @react-router/express@7.2.0-pre.2

create-react-router@7.2.0-pre.2