Release 1.13.0

Release that allows to use the functionality of this library in Modals on Android, adds offset property to KeyboardGestureArea component, gives an ability to prevent default actions from being fired in KeyboardToolbar, brings support for [email protected], contains a lot of other bug fixes and improves the stability of the library. Read more about all changes in blogpost 🎉

🐛 Bug fixes

• proper ref deallocation with FlatList -> KeyboardAwareScrollView usage (e79dbc7) closes #525
• KeyboardToolbar accessibility wording (ef2f58c)
• instant keyboard hide causes KeyboardAvoidingView keeping bottom space (6861faf)
• web compilation (10a90ae)

👍 Improvements

• modal support on Android (4a796eb) closes #369 #387
• react on StatusBar.translucent changes (265b93c) closes #526
• new offset prop for KeyboardGestureArea on Android (2f901a9)
• allow keyboard toolbar button callbacks to cancel default actions (36b704b)
• synchronous handler mount (cfc62b7)
• support for react-native version 0.75 (c2a635b)

🔢 Miscellaneous

• missing permissions for publishing package from CI (72c9fed)
• allow manual publishing of the package from CI (a2abcd2)
• add e2e tests for native-stack screen (2729e28)
• update detox (bdaa38e)
• run e2e tests on iOS 16 and iOS 18 08efc81
• add KeyboardToolBarTheme type example (1bce3c8)
• minor eslint tweaks (bb43792)
• added interactive keyword to docs, improve SEO search (54dc6d7)
• bump minimal react-native-reanimated version (23b0466)
• hook names truncated in docs menu bar (e6ea67f)
• use docusaurus 3.4.0 (a265bf0)
• blogpost for 1.13.0 (b4eef45)
• checkout 1.13.0 docs (7fcb6b7)

🚨⚠️🚨 Caution 🚨⚠️🚨

This release doesn't have any breaking changes. However if you used undocumented setKeyboardHandlers/setInputHandlers method (from context/useKeyboardContext), then, please, be aware that the signature of the method was changed:

const context = useKeyboardContext();

// ...

-context.setKeyboardHandlers({ [key]: handler });
+const cleanup = context.setKeyboardHandlers(handler);

But since it was not documented and mostly was used by internal hooks - this change is not treated as a breaking one.