Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update version for release #11035

Merged
merged 2 commits into from
Nov 16, 2023

Conversation

github-actions[bot]
Copy link
Contributor

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.19.0

Minor Changes

  • Add unstable_flushSync option to useNavigate/useSumbit/fetcher.load/fetcher.submit to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#11005)
  • Remove the unstable_ prefix from the useBlocker hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix from unstable_usePrompt due to differences in how browsers handle window.confirm that prevent React Router from guaranteeing consistent/correct behavior. (#10991)

Patch Changes

  • Fix useActionData so it returns proper contextual action data and not any action data in the tree (#11023)

  • Fix bug in useResolvedPath that would cause useResolvedPath(".") in a splat route to lose the splat portion of the URL path. (#10983)

    • ⚠️ This fixes a quite long-standing bug specifically for "." paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via "." inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.
  • Updated dependencies:

    • @remix-run/router@1.12.0

react-router-dom@6.19.0

Minor Changes

  • Add unstable_flushSync option to useNavigate/useSumbit/fetcher.load/fetcher.submit to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#11005)
  • Allow unstable_usePrompt to accept a BlockerFunction in addition to a boolean (#10991)

Patch Changes

  • Fix issue where a changing fetcher key in a useFetcher that remains mounted wasn't getting picked up (#11009)
  • Fix useFormAction which was incorrectly inheriting the ?index query param from child route action submissions (#11025)
  • Fix NavLink active logic when to location has a trailing slash (#10734)
  • Updated dependencies:
    • react-router@6.19.0
    • @remix-run/router@1.12.0

@remix-run/router@1.12.0

Minor Changes

  • Add unstable_flushSync option to router.navigate and router.fetch to tell the React Router layer to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#11005)

Patch Changes

  • Fix relative="path" bug where relative path calculations started from the full location pathname, instead of from the current contextual route pathname. (#11006)

    <Route path="/a">
      <Route path="/b" element={<Component />}>
        <Route path="/c" />
      </Route>
    </Route>;
    
    function Component() {
      return (
        <>
          {/* This is now correctly relative to /a/b, not /a/b/c */}
          <Link to=".." relative="path" />
          <Outlet />
        </>
      );
    }

react-router-dom-v5-compat@6.19.0

Patch Changes

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

react-router-native@6.19.0

Patch Changes

  • Updated dependencies:
    • react-router@6.19.0

@brophdawg11 brophdawg11 merged commit dcf0c2a into release-next Nov 16, 2023
3 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch November 16, 2023 14:41
jonathanpruvost pushed a commit to concordnow/react-router that referenced this pull request Nov 28, 2023
* chore: Update version for release

* Update changelogs

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Matt Brophy <matt@brophy.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant