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 #12121

Merged
merged 2 commits into from
Oct 11, 2024
Merged

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-v6, this PR will be updated.

Releases

react-router@6.27.0

Minor Changes

  • Stabilize unstable_patchRoutesOnNavigation (#11973)
  • Stabilize unstable_dataStrategy (#11974)
  • Stabilize the unstable_flushSync option for navigations and fetchers (#11989)
  • Stabilize the unstable_viewTransition option for navigations and the corresponding unstable_useViewTransitionState hook (#11989)

Patch Changes

    • Fix bug when submitting to the current contextual route (parent route with an index child) when an ?index param already exists from a prior submission (#12003)
    • Fix useFormAction bug - when removing ?index param it would not keep other non-Remix index params
    • Fix types for RouteObject within PatchRoutesOnNavigationFunction's patch method so it doesn't expect agnostic route objects passed to patch (#11967)
    • Add new PatchRoutesOnNavigationFunctionArgs type for convenience
  • Updated dependencies:
    • @remix-run/router@1.20.0

react-router-dom@6.27.0

Minor Changes

  • Stabilize unstable_patchRoutesOnNavigation (#11973)
  • Stabilize unstable_dataStrategy (#11974)
  • Stabilize the unstable_flushSync option for navigations and fetchers (#11989)
  • Stabilize the unstable_viewTransition option for navigations and the corresponding unstable_useViewTransitionState hook (#11989)

Patch Changes

    • Fix bug when submitting to the current contextual route (parent route with an index child) when an ?index param already exists from a prior submission (#12003)
    • Fix useFormAction bug - when removing ?index param it would not keep other non-Remix index params
    • Fix types for RouteObject within PatchRoutesOnNavigationFunction's patch method so it doesn't expect agnostic route objects passed to patch (#11967)
    • Add new PatchRoutesOnNavigationFunctionArgs type for convenience
  • Updated dependencies:
    • react-router@6.27.0
    • @remix-run/router@1.20.0

@remix-run/router@1.20.0

Minor Changes

  • Stabilize unstable_patchRoutesOnNavigation (#11973)
  • Stabilize unstable_dataStrategy (#11974)
  • Stabilize the unstable_flushSync option for navigations and fetchers (#11989)
  • Stabilize the unstable_viewTransition option for navigations and the corresponding unstable_useViewTransitionState hook (#11989)

Patch Changes

    • Fix bug when submitting to the current contextual route (parent route with an index child) when an ?index param already exists from a prior submission (#12003)
    • Fix useFormAction bug - when removing ?index param it would not keep other non-Remix index params
  • Fix bug with fetchers not persisting preventScrollReset through redirects during concurrent fetches (#11999)

  • Remove internal cache to fix issues with interrupted patchRoutesOnNavigation calls (#12055)

    • We used to cache in-progress calls to patchRoutesOnNavigation internally so that multiple navigations with the same start/end would only execute the function once and use the same promise
    • However, this approach was at odds with patch short circuiting if a navigation was interrupted (and the request.signal aborted) since the first invocation's patch would no-op
    • This cache also made some assumptions as to what a valid cache key might be - and is oblivious to any other application-state changes that may have occurred
    • So, the cache has been removed because in most cases, repeated calls to something like import() for async routes will already be cached automatically - and if not it's easy enough for users to implement this cache in userland
  • Avoid unnecessary console.error on fetcher abort due to back-to-back revalidation calls (#12050)

  • Expose errors thrown from patchRoutesOnNavigation directly to useRouteError instead of wrapping them in a 400 ErrorResponse instance (#12111)

    • Fix types for RouteObject within PatchRoutesOnNavigationFunction's patch method so it doesn't expect agnostic route objects passed to patch (#11967)
    • Add new PatchRoutesOnNavigationFunctionArgs type for convenience
  • Fix bugs with partialHydration when hydrating with errors (#12070)

  • Remove internal discoveredRoutes FIFO queue from unstable_patchRoutesOnNavigation (#11977)

react-router-dom-v5-compat@6.27.0

Patch Changes

  • Updated dependencies:
    • react-router-dom@6.27.0
    • react-router@6.27.0
    • @remix-run/router@1.20.0

react-router-native@6.27.0

Patch Changes

  • Updated dependencies:
    • react-router@6.27.0

@brophdawg11 brophdawg11 merged commit 8cfb4a7 into release-v6 Oct 11, 2024
3 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-v6 branch October 11, 2024 18:06
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