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.