Question: Will React Native SDK catch up with openim-sdk-core v3.8.3-patch.15 / version alignment roadmap?

Question / 问题

openim-sdk-core has already released v3.8.3-patch.15 (2026-08-07), while the latest @openim/rn-client-sdk is still 3.8.3-patch.12.4 (GitHub release 2026-04-30).

We saw the clarification in #100 that React Native SDK is still officially supported and will continue to be maintained, and #101 confirmed RN 0.87 / New Architecture compatibility for patch.12.4. This question is specifically about core version catch-up.

Could the maintainers please clarify:

1. Will @openim/rn-client-sdk be updated to align with openim-sdk-core v3.8.3-patch.15 (or newer)?
2. What is the official version alignment policy between openim-sdk-core and the React Native SDK (Android AAR / iOS XCFramework via gomobile)?
3. For production RN apps targeting a server on v3.8.3-patch.15, is rn-client-sdk@3.8.3-patch.12.4 considered supported / safe, or should we wait for a newer RN binding?
4. Is there an approximate timeline or roadmap for RN SDK catching up with core (including any planned TurboModules migration mentioned in #101)?

openim-sdk-core 已发布到 v3.8.3-patch.15，而 @openim/rn-client-sdk 最新仍是 3.8.3-patch.12.4。

我们已看到 #100 确认 RN SDK 仍会官方维护，以及 #101 对 patch.12.4 的 RN 0.87 兼容说明。本次主要想确认 与 core 版本跟进 的计划：

1. RN SDK 是否会跟进到与 core v3.8.3-patch.15（或更新版本）对齐？
2. core 与 RN SDK（Android AAR / iOS XCFramework）的官方版本对齐策略是怎样的？
3. 服务端已用 v3.8.3-patch.15 时，生产环境继续用 rn-client-sdk@3.8.3-patch.12.4 是否仍被支持 / 安全，还是应等待更新的 RN binding？
4. 是否有大致跟进时间表或 roadmap（含 #101 提到的后续 TurboModules 迁移）？

Thanks!

Start by reviewing the version relationship between openim-sdk-core v3.8.3-patch.15 and @openim/rn-client-sdk 3.8.3-patch.12.4, including the Android AAR, iOS XCFramework, and planned TurboModules migration referenced in #101. Done means documenting the official alignment policy, production compatibility guidance, and any roadmap or timeline; #100 and #101 provide relevant context.