fix(apps): older-version install no longer pins row as up-to-date#567
Conversation
updateAppVersion was stamping latest* fields to the picked tag, so an explicit older-version install (Details → pick older release → Install) made installedVersionCode == latestVersionCode. The checkForUpdates versionCode-parity canary then forced isUpdateAvailable = false forever and the apps row claimed 'latest installed'. Recompute the flag against the existing upstream snapshot instead and leave latest* untouched so the next periodic check resolves the true latest from the feed.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughRecomputes update availability when installing a tag (avoids stamping latest* metadata), adds a Room schema snapshot for DB version 16, changes first-install behavior to leave latest* fields null, and includes minor import/formatting edits. ChangesUpdate Available Recalculation Fix
Formatting and Import Cleanup
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Three follow-ups missed by #559's merge:
updateAppVersionno longer stampslatest*to the picked tag. Installing an explicitly older release (Details → pick → Install) was poisoninglatestVersionCode, so thecheckForUpdatesversionCode-parity canary forced the update badge off forever. Now recomputesisUpdateAvailableagainst the existing upstream snapshot viaVersionMath.isVersionNewerand leaveslatest*for the next periodic check to resolve from the feed.Summary by CodeRabbit
Bug Fixes
Chores