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

[email protected]

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]

[email protected]

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies:
  • [email protected]

@remix-run/[email protected]

Patch Changes

• Update the unstable_dataStrategy API to allow for more advanced implementations (#11943)

  • Rename unstable_HandlerResult to unstable_DataStrategyResult
  • The return signature has changed from a parallel array of unstable_DataStrategyResult[] (parallel to matches) to a key/value object of routeId => unstable_DataStrategyResult
    • This allows you to more easily decide to opt-into or out-of revalidating data that may not have been revalidated by default (via match.shouldLoad)
    • ⚠️ This is a breaking change if you've currently adopted unstable_dataStrategy
  • Added a new fetcherKey parameter to unstable_dataStrategy to allow differentiation from navigational and fetcher calls
  • You should now return/throw a result from your handlerOverride instead of returning a DataStrategyResult
    • If you are aggregating the results of match.resolve() into a final results object you should not need to think about the DataStrategyResult type
    • If you are manually filling your results object from within your handlerOverride, then you will need to assign a DataStrategyResult as the value so React Router knows if it's a successful execution or an error.

• Preserve view transition through redirects (#11925)

• Fix blocker usage when blocker.proceed is called quickly/syncronously (#11930)

• Preserve pending view transitions through a router revalidation call (#11917)