chore: Update version for release

[mcansh]

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

react-router@6.5.0

Minor Changes

• Allows optional routes and optional static segments (#9650)

  Optional params examples

  :lang?/about will get expanded matched with

  /:lang/about
  /about
  

  /multistep/:widget1?/widget2?/widget3?
  Will get expanded matched with:

  /multistep
  /multistep/:widget1
  /multistep/:widget1/:widget2
  /multistep/:widget1/:widget2/:widget3
  

  optional static segment example

  /fr?/about will get expanded and matched with:

  /about
  /fr/about
  

Patch Changes

• Stop incorrectly matching on partial named parameters, i.e. <Route path="prefix-:param">, to align with how splat parameters work. If you were previously relying on this behavior then it's recommended to extract the static portion of the path at the useParams call site: (#9506)

  // Old behavior at URL /prefix-123
  <Route path="prefix-:id" element={<Comp /> }>
  
  function Comp() {
    let params = useParams(); // { id: '123' }
    let id = params.id; // "123"
    ...
  }
  
  // New behavior at URL /prefix-123
  <Route path=":id" element={<Comp /> }>
  
  function Comp() {
    let params = useParams(); // { id: 'prefix-123' }
    let id = params.id.replace(/^prefix-/, ''); // "123"
    ...
  }

• Updated dependencies:

  • @remix-run/router@1.1.0

@remix-run/router@1.1.0

Minor Changes

• Allows optional routes and optional static segments (#9650)

  Optional params examples

  :lang?/about will get expanded matched with

  /:lang/about
  /about
  

  /multistep/:widget1?/widget2?/widget3?
  Will get expanded matched with:

  /multistep
  /multistep/:widget1
  /multistep/:widget1/:widget2
  /multistep/:widget1/:widget2/:widget3
  

  optional static segment example

  /fr?/about will get expanded and matched with:

  /about
  /fr/about
  

Patch Changes

• Stop incorrectly matching on partial named parameters, i.e. <Route path="prefix-:param">, to align with how splat parameters work. If you were previously relying on this behavior then it's recommended to extract the static portion of the path at the useParams call site: (#9506)

  // Old behavior at URL /prefix-123
  <Route path="prefix-:id" element={<Comp /> }>
  
  function Comp() {
    let params = useParams(); // { id: '123' }
    let id = params.id; // "123"
    ...
  }
  
  // New behavior at URL /prefix-123
  <Route path=":id" element={<Comp /> }>
  
  function Comp() {
    let params = useParams(); // { id: 'prefix-123' }
    let id = params.id.replace(/^prefix-/, ''); // "123"
    ...
  }

• Persist headers on loader request's after SSR document action request (#9721)

• Fix requests sent to revalidating loaders so they reflect a GET request (#9660)

• Fix issue with deeply nested optional segments (#9727)

• GET forms now expose a submission on the loading navigation (#9695)

• Fix error boundary tracking for multiple errors bubbling to the same boundary (#9702)

react-router-dom@6.5.0

Patch Changes

• Updated dependencies:
  • react-router@6.5.0
  • @remix-run/router@1.1.0

react-router-dom-v5-compat@6.5.0

Patch Changes

• Updated dependencies:
  • react-router@6.5.0
  • react-router-dom@6.5.0

react-router-native@6.5.0

Patch Changes

• Updated dependencies:
  • react-router@6.5.0