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

Minor Changes

• Add a new unstable_dataStrategy configuration option (#11098)

  • This option allows Data Router applications to take control over the approach for executing route loaders and actions
  • The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.16.0-pre.0

react-router-dom@6.23.0-pre.0

Minor Changes

• Add a new unstable_dataStrategy configuration option (#11098)

  • This option allows Data Router applications to take control over the approach for executing route loaders and actions
  • The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.16.0-pre.0
  • react-router@6.23.0-pre.0

react-router-dom-v5-compat@6.23.0-pre.0

Minor Changes

• Add a new unstable_dataStrategy configuration option (#11098)

  • This option allows Data Router applications to take control over the approach for executing route loaders and actions
  • The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.16.0-pre.0
  • react-router@6.23.0-pre.0
  • react-router-dom@6.23.0-pre.0

react-router-native@6.23.0-pre.0

Minor Changes

• Add a new unstable_dataStrategy configuration option (#11098)

  • This option allows Data Router applications to take control over the approach for executing route loaders and actions
  • The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more

Patch Changes

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

@remix-run/router@1.16.0-pre.0

Minor Changes

• Add a new unstable_dataStrategy configuration option (#11098)

  • This option allows Data Router applications to take control over the approach for executing route loaders and actions
  • The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more

• Add a new future.unstable_skipActionRevalidation future flag (#11098)

  • Currently, active loaders revalidate after any action, regardless of the result
  • With this flag enabled, actions that return/throw a 4xx/5xx response status will no longer automatically revalidate
  • This should reduce load on your server since it's rare that a 4xx/5xx should actually mutate any data
  • If you need to revalidate after a 4xx/5xx result with this flag enabled, you can still do that via returning true from shouldRevalidate
  • shouldRevalidate now also receives a new unstable_actionStatus argument alongside actionResult so you can make decision based on the status of the action response without having to encode it into the action data
• • Move unstable_dataStrategy from createStaticHandler to staticHandler.query so it can be request-specific for use with the ResponseStub approach in Remix. It's not really applicable to queryRoute for now since that's a singular handler call anyway so any pre-processing/post/processing could be done there manually. (#11377)
  • Added a new skipLoaders flag to staticHandler.query for calling only the action in Remix Single Fetch

• Added 2 new options to the staticHandler.query method for use in Remix's Single Fetch implementation: (#11098)

  • loadRouteIds: An optional array of route IDs to load if you wish to load a subset of the matched routes (useful for fine-grained revalidation)
  • skipLoaderErrorBubbling: Disable error bubbling on loader executions for single-fetch scenarios where the client-side router will handle the bubbling