Repository navigation
Update mobile 0.0.43 Android download links - #14696
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughUpdated Android APK download links from earlier releases to Merge Risk: ⚪ Minimal · up to This localized change updates Android download links to the published 0.0.43 release without changing application behavior; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 7bda057d-ab20-41bd-a853-5a3d09f2bdff
📒 Files selected for processing (9)
README.mddocs/readme/README.es.mddocs/readme/README.fr.mddocs/readme/README.ja.mddocs/readme/README.ko.mddocs/readme/README.pt.mddocs/readme/README.zh-CN.mdsrc/renderer/src/components/mobile/mobile-platform-copy.tssrc/renderer/src/components/settings/MobileSettingsPane.tsx
* Update mobile 0.0.43 Android download links * Sync French and Portuguese APK labels to 0.0.43
ELI5
Android 0.0.43 is published, so every "Download the APK" link should point at it. Most of them were still pointing at 0.0.37 — six versions behind.
What Changed
Point all hardcoded Android APK links at the published
mobile-android-v0.0.43release, and update the version shown in the link text where it appears.README.md(was 0.0.42)docs/readme/README.es.md,README.fr.md,README.ja.md,README.ko.md,README.pt.md,README.zh-CN.md(all were 0.0.37)src/renderer/src/components/settings/MobileSettingsPane.tsx(was 0.0.37)src/renderer/src/components/mobile/mobile-platform-copy.ts(was 0.0.37)Why
mobile-android-v0.0.43is published with anapp-release.apkasset: https://github.com/stablyai/orca/releases/tag/mobile-android-v0.0.43Android 0.0.43 matches what iOS users are already running — both platforms shipped from the same commit — and carries three P0 fixes Android users did not have: the blank terminal after leaving a chat tab (#14179), a terminal republished as an agent chat surface from stale PTY launch provenance (#14244), and split-pane identity bleed that put one pane's agent title on its sibling (#14247).
Worth noting the translated READMEs had drifted much further than the English one: the in-app links and all six translations were still on 0.0.37, so users following any non-English README were four releases behind what the main README offered.
Linked Issue
N/A — release follow-up for the published
mobile-android-v0.0.43release.Visual Proof
N/A— link/URL updates only. The in-app strings are the same UI in the same place, pointing at a newer release.Testing
Verified the new asset URL resolves before changing anything:
curl -sI -L -o /dev/null -w "%{http_code}" https://github.com/stablyai/orca/releases/download/mobile-android-v0.0.43/app-release.apk→ 200Confirmed the GitHub release exists with an
app-release.apkasset viagh release view.Re-ran the search after editing; no
mobile-android-v0.0.37/v0.0.42references remain inREADME.md,docs/readme, orsrc.oxlint, react-doctor, andoxfmtran clean on the two changed TypeScript files via the pre-commit hook.I manually tested these changes locally
Automated tests added/updated, or explained why not below
No automated test: these are hardcoded URL constants with no behavior to assert. A test pinning the version string would need updating every release for no added safety. The real gap is that this list is maintained by hand at all — see below.
AI Disclosure
N/A — internal contributor.
Review
Ensure no issues in: Security, Cross-platoform support (Linux, Windows, Mac), Remote SSH, Mobile, general backwards compatibility, performance
Link-only change. No runtime, wire-format, SSH, or platform-specific behavior.
Checklist
N/Awith reasonpnpm lint,pnpm typecheck,pnpm test, andpnpm buildpass (or CI will cover; local preferred)Follow-up worth considering
These nine locations drift every release and were four versions stale here. Deriving the URL from a single constant, or adding a CI check that the referenced tag matches the latest
mobile-android-v*release, would stop this recurring.