Repository navigation
chore(mobile): bump web/mobile version to 0.113.0 - #6171
Conversation
The v0.113.0 bump commit predates #6065, which added the web/mobile bump step to the release-branch workflow, so the mobile app still reported v0.112.3 in its drawer (M1 in the v0.113.0 QA). Align it with oss and ee.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 4 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe mobile package version changes from ChangesMobile package version
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a one-line mobile version metadata correction; no actionable merge-blocking risk remains after the normal workspace check. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Railway Preview Environment
Updated at 2026-08-21T18:00:44.387Z |
Context
The v0.113.0 version bump commit landed before #6065, and #6065 is what added the
web/mobilebump step to the release-branch workflow. Soweb/mobile/package.jsonstill says 0.112.3 while oss and ee say 0.113.0, and the mobile app's drawer reports v0.112.3 on the v0.113.0 stages (finding M1 in the release QA).Change
One line:
web/mobile/package.jsonversion 0.112.3 -> 0.113.0. No lockfile change (workspace packages' own versions are not recorded there).QA
On staging
/m, open the drawer: it must read v0.113.0 after the next deploy.