6.0.18 (2023-02-26)

Bug Fixes

• fix paths in sourcemap files (42c906d) - by @

6.2.15 (2023-02-26)

Bug Fixes

• fix paths in sourcemap files (42c906d) - by @

6.4.8 (2023-02-26)

Bug Fixes

• fix paths in sourcemap files (42c906d) - by @

3.4.1 (2023-02-26)

Bug Fixes

• fix paths in sourcemap files (42c906d) - by @

1.3.23 (2023-02-26)

Note: Version bump only for package flipper-plugin-react-navigation

1.3.17 (2023-02-26)

Bug Fixes

• fix paths in sourcemap files (42c906d) - by @

6.0.4 (2023-02-26)

Note: Version bump only for package @react-navigation/example

6.4.7 (2023-02-23)

Note: Version bump only for package @react-navigation/core

6.3.15 (2023-02-23)

Note: Version bump only for package @react-navigation/stack

6.5.6 (2023-02-23)

Note: Version bump only for package @react-navigation/bottom-tabs

6.9.11 (2023-02-23)

Bug Fixes

• fix headerBackVisible type annotation (#11220) (fac8f32) - by @Vin-Xi

6.6.1 (2023-02-23)

Note: Version bump only for package @react-navigation/drawer

6.2.14 (2023-02-23)

Note: Version bump only for package @react-navigation/material-bottom-tabs

6.6.1 (2023-02-23)

Note: Version bump only for package @react-navigation/material-top-tabs

1.3.16 (2023-02-23)

Note: Version bump only for package @react-navigation/elements

6.1.5 (2023-02-23)

Note: Version bump only for package @react-navigation/native

6.1.7 (2023-02-23)

Bug Fixes

• handle getId in tab and drawer routers (4e2d6d8) - by @

1.3.22 (2023-02-23)

Note: Version bump only for package flipper-plugin-react-navigation

6.0.17 (2023-02-23)

Note: Version bump only for package @react-navigation/devtools

7.0.0-alpha.0 (2023-02-17)

Bug Fixes

• add ScrollView type to 'getScrollResponder' (#11112) (f4324cd) - by @ken0nek

• don't modify browser history on re-render (ab66777) - by @satya164

• keep hash/fragment section un URLs on web (#11078) (a30daa0) - by @nikgraf

• refactor!: improve the API for Link component (7f35837) - by @satya164

• fix!: align onReady callback and navigationRef.isReady (1959baa) - by @satya164

Features

• make useScrollToTop work when nesting multiple tab navigators (#11063) (dce463a), closes /github.com/react-navigation/react-navigation/pull/9434#issuecomment-1328345015 - by @anthonyguay
• support statically confguring navigation tree (#11144) (4cc322e) - by @satya164

BREAKING CHANGES

• Initially the Link component was designed to work with path strings via the to prop. But it has few issues:

• The path strings are not type-safe, making it easy to cause typos and bugs after
  refactor
• The API made navigating via screen name more incovenient, even if that's the preferred approach

This revamps the API of the Link component to make it easier to use. Instead of to prop, it now accepts screen and params props, as well as an optional href prop to
use instead of the generated path.

e.g.:

<Link screen="Details" params={{ foo: 42 }}>Go to Details</Link>

This also drops the useLinkTo hook and consolidates into the useLinkTools hook - which lets us build a href for a screen or action for a path.

• Previously, the onReady prop and navigationRef.isReady() work slightly
  differently. The
  onReady callback fired when NavigationContainer finishes mounting and deep links is resolved.
  The navigationRef.isReady() method additionally checks if there are any navigators rendered - which may not be true if the user is rendering their navigators conditionally inside a
  NavigationContainer.

This changes onReady to work similar to navigationRef.isReady(). The onReady callback will now fire only when there are navigators rendered - reflecting the value of
navigationRef.isReady().