fix: Docs/mobile rum stable versions - #533
Merged
Merged
Conversation
The Mobile RUM guides still documented pre-release versions. All three SDKs have since shipped their first stable release, so every pinned coordinate and the surrounding alpha framing was out of date. Versions verified against the registries: - React Native: 0.1.0-alpha.5 -> 0.1.1 (npm dist-tag latest). The two companion packages, mobile-react-native-session-replay and mobile-react-navigation, are also 0.1.1. - Android: 0.1.0-alpha5 -> 0.1.0 across all seven ai.openobserve artifacts (Maven Central <release>). - iOS: 0.1.0-alpha.4 -> 0.1.0 for the SPM tag and every CocoaPods pod. Both stable releases are code-identical to the alphas they replace -- the Android and iOS release commits only bump version strings -- so the documented APIs and every remaining limitation still hold. The 'in this alpha' caveats are therefore rewritten to name the release rather than dropped: managed-cloud site presets, dSYM upload tooling, the Gradle plugin DSL, and experimental SwiftUI tracking are all still pending as of 0.1.0. Also corrected while verifying: - The React Native layer-alignment guidance claimed the npm version and its native versions must match. They deliberately differ: 0.1.1 pins Android and iOS 0.1.0, per NATIVE_SDK_VERSIONS.md. Reworded to say the package brings its own native pins. - The SPM snippet in ios.md used 'from: "0.1.0-alpha.4"', a floating range that contradicts the pin-exact advice two lines above it. Now 'exact:'. - react-native.md omitted the upper bound on the react-native peer range, which is '>=0.63.4 <1.0'. - The Gradle plugin notes now say it is not yet published alongside the 0.1.0 artifacts (confirmed: 404 on Maven Central), not merely that its DSL is unfinished.
Marks mobile RUM as Beta to match how Data Sources labels it in the product, without threading a status badge through the body of eight pages. The tag lives in the bracket of the existing top-of-page callout — 'Version (Beta)' — so there is one place to edit when the SDKs go GA. The callout bodies previously read 'the first stable release', which would have contradicted the tag directly above them, so that phrasing is dropped in favour of stating the versions plainly. Same for the two production-readiness FAQs, which now answer Beta rather than first stable release. Versions are unchanged and still match the registries.
Contributor
|
✅ Preview Ready! |
nikhilsaikethe
approved these changes
Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.