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

Bug Fixes

• Check cardStyleInterpolator name to allow for custom animation as well (#11209) (c733ad5), closes /github.com/react-navigation/react-navigation/blob/main/packages/stack/src/TransitionConfigs/CardStyleInterpolators.tsx#L93 /github.com/react-navigation/react-navigation/blob/main/packages/stack/src/views/Stack/Card.tsx#L580 - by @drager

• fix checking for modal presentation in stack (639d6c8) - by @satya164

• refactor!: drop support for key property in navigate (61c53bb) - by @satya164

BREAKING CHANGES

• Previously, you could specify a route key to navigate to, e.g.
  navigation.navigate({ key: 'someuniquekey' }). It's problematic since key is an internal
  implementation detail and created by the library internally - which makes it weird to use. None
  of the other actions support such usage either.

In addition, we have already added a better API (getId) which can be used for similar use
cases - and gives users full control since they provide the ID and it's not autogenerated by the
library.

So this change removes the key option from the navigate action.

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

Bug Fixes

• bump query-string version (#11069) (e6c05e2) - by @krudos

• fix type of setOptions and mark data passed to callbacks as Readonly (6655c66) - by @satya164

• remove defaultScreenOptions from default navigator options (6267952) - by @satya164

• support dispatching action to child without 'navigationInChildEnabled' if 'target' is specified (debd620) - by @satya164

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

• feat!: add popTo method for stack and remove going back behaviour of (c9c2163) - by @satya164

• refactor!: drop support for key property in navigate (61c53bb) - by @satya164

Features

• add navigateDeprecated for backward compatibility (8ea6dc7) - by @satya164
• extract drawer to a separate package (58b7cae) - by @satya164
• support statically confguring navigation tree (#11144) (4cc322e) - by @satya164

BREAKING CHANGES

• 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().

• Previously, navigate method navigated back if the screen
  already exists in the stack. I have seen many people get confused by this
  behavior. This behavior is also used for sending params to a previous
  screen in the documentation. However, it's also problematic since it could
  either push or pop the screens based on the scenario.

This removes the going back behavior from navigate and adds a new method
popTo to go back to a specific screen in the stack.

The methods now behave as follows:

• navigate(screenName) will stay on the current screen if the screen is
  already focused, otherwise push a new screen to the stack.
• popTo(screenName) will go back to the screen if it exists in the stack,
  otherwise pop the current screen and add this screen to the stack.
• To achieve the previous behavior with navigate, you can use the getId
  prop in which case it'll go to the screen with the matching ID and push or
  pop screens accordingly.

• Previously, you could specify a route key to navigate to, e.g.
  navigation.navigate({ key: 'someuniquekey' }). It's problematic since key is an internal
  implementation detail and created by the library internally - which makes it weird to use. None
  of the other actions support such usage either.

In addition, we have already added a better API (getId) which can be used for similar use
cases - and gives users full control since they provide the ID and it's not autogenerated by the
library.

So this change removes the key option from the navigate action.

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

Bug Fixes

• added close drawer accessibility tap area (#11184) (20ec204) - by @mikegarfinkle
• drawerstatuscontext should be exported (#11041) (6e4cb06) - by @leonchabbey
• fix overlay not receiving clicks on web (666c8db) - by @satya164

Code Refactoring

• drop react-native-flipper-plugin (643b8e8), closes /github.com/react-native-community/discussions-and-proposals/discussions/546#discussioncomment-4178951 - by @satya164

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

Features

• add testID and accessibilityLabel to DrawerItem (#11168) (4471fa0) - by @andrewtremblay
• extract drawer to a separate package (58b7cae) - 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.

• React Native team is focusing on migrating away from Flipper. So it doesn't make much sense for us to spend additional resources to support the Flipper plugin.

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

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

Features

• expose the original label in children prop for custom label functions in tab navigators (a6fd49f) - 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.

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

Bug Fixes

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

• make headerBackground visible with transparent header (#11109) (2b1e8dc) - by @yhkaplan

• refactor!: improve the API for Link component (7f35837) - 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.

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

Bug Fixes

• handle merge: true with NAVIGATION_DEPRECATED in TabRouter (e5cf73d) - by @satya164

• feat!: add popTo method for stack and remove going back behaviour of (c9c2163) - by @satya164

• refactor!: drop support for key property in navigate (61c53bb) - by @satya164

Features

• add navigateDeprecated for backward compatibility (8ea6dc7) - by @satya164
• extract drawer to a separate package (58b7cae) - by @satya164

BREAKING CHANGES

• Previously, navigate method navigated back if the screen
  already exists in the stack. I have seen many people get confused by this
  behavior. This behavior is also used for sending params to a previous
  screen in the documentation. However, it's also problematic since it could
  either push or pop the screens based on the scenario.

This removes the going back behavior from navigate and adds a new method
popTo to go back to a specific screen in the stack.

The methods now behave as follows:

• navigate(screenName) will stay on the current screen if the screen is
  already focused, otherwise push a new screen to the stack.
• popTo(screenName) will go back to the screen if it exists in the stack,
  otherwise pop the current screen and add this screen to the stack.
• To achieve the previous behavior with navigate, you can use the getId
  prop in which case it'll go to the screen with the matching ID and push or
  pop screens accordingly.

• Previously, you could specify a route key to navigate to, e.g.
  navigation.navigate({ key: 'someuniquekey' }). It's problematic since key is an internal
  implementation detail and created by the library internally - which makes it weird to use. None
  of the other actions support such usage either.

In addition, we have already added a better API (getId) which can be used for similar use
cases - and gives users full control since they provide the ID and it's not autogenerated by the
library.

So this change removes the key option from the navigate action.

3.1.0 (2023-02-17)

Bug Fixes

• added close drawer accessibility tap area (#11184) (20ec204) - by @mikegarfinkle

Features

• extract drawer to a separate package (58b7cae) - by @satya164

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

Code Refactoring

• move tab-view to direct dependency of material-top-tabs (2bd585b) - by @satya164

Features

• allow users to pass android_ripple config in TabView (#11203) (15939d8), closes #11198 - by @okwasniewski
• expose tabBarGap option in material top tabs (#11038) (29818a8) - by @mlecoq
• expose the original label in children prop for custom label functions in tab navigators (a6fd49f) - by @satya164

BREAKING CHANGES

• This change will simplify installation of material-top-tabs, but that means user's version won't be used anymore. If users need to force specific version, they can use yarn's resolutions or npm's overrides feature.

3.5.0 (2023-02-17)

Bug Fixes

• split updating state to batches on long lists (#11046) (0aa6a18) - by @okwasniewski

Features

• add support to override pager's overScrollMode (#11194) (0c4e83a) - by @ouabing
• allow users to pass android_ripple config in TabView (#11203) (15939d8), closes #11198 - by @okwasniewski
• extract drawer to a separate package (58b7cae) - by @satya164

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

Code Refactoring

• drop react-native-flipper-plugin (643b8e8), closes /github.com/react-native-community/discussions-and-proposals/discussions/546#discussioncomment-4178951 - by @satya164

BREAKING CHANGES

• React Native team is focusing on migrating away from Flipper. So it doesn't make much sense for us to spend additional resources to support the Flipper plugin.

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

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

6.3.14 (2023-02-16)

Bug Fixes

• fix checking for modal presentation in stack (b0253c3) - by @satya164

3.4.0 (2023-02-14)

Features

• add support to override pager's overScrollMode (#11194) (8d60b3c) - by @ouabing
• allow users to pass android_ripple config in TabView (#11203) (a452ecb), closes #11198 - by @okwasniewski

6.3.13 (2023-02-14)

Bug Fixes

• Check cardStyleInterpolator name to allow for custom animation as well (#11209) (a5050ba), closes /github.com/react-navigation/react-navigation/blob/main/packages/stack/src/TransitionConfigs/CardStyleInterpolators.tsx#L93 /github.com/react-navigation/react-navigation/blob/main/packages/stack/src/views/Stack/Card.tsx#L580 - by @drager

6.5.5 (2023-02-14)

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

6.6.0 (2023-02-14)

Bug Fixes

• added close drawer accessibility tap area (#11184) (061fb13) - by @mikegarfinkle

Features

• add testID and accessibilityLabel to DrawerItem (#11168) (99ff9f7) - by @andrewtremblay

6.1.4 (2023-02-14)

Bug Fixes

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

6.0.3 (2023-02-14)

Bug Fixes

• added close drawer accessibility tap area (#11184) (061fb13) - by @mikegarfinkle

6.6.0 (2023-02-14)

Features

• allow users to pass android_ripple config in TabView (#11203) (a452ecb), closes #11198 - by @okwasniewski

6.9.10 (2023-02-14)

Bug Fixes

• make headerBackground visible with transparent header (#11109) (d7ef2bf) - by @yhkaplan