hc - Feedback

Why GitHub is ahead of Play Store GitHub/FOSS releases are fully automated on every version tag. Play Store releases are manual and go through Google review — especially slow for health apps with sensitive permissions. Current lag: Play Store is ~8–9 releases behind GitHub release Intentional model: FOSS = bleeding edge for contributors and power users. Play Store = stable channel, released in batches once changes are validated. Going forward, Google Play updates will follow a predictable cadence: Play Store releases will ship every 3–4 FOSS patch versions, once those FOSS releases have been stable with no reported regressions or open critical issues. How it works: - FOSS (GitHub Releases) remains the bleeding-edge channel — every tagged release ships there automatically. - Play Store updates are batched: after 3–4 stable FOSS patches with no outstanding issues, the Play Store build is submitted. - “Stable” means no open critical bugs or regressions tied to the versions since the last Play Store release. If something breaks on FOSS, the Play Store batch waits until it’s fixed. Expected lag: Play Store will typically be 3–4 patch versions behind GitHub at most, plus Google’s review time (usually a few days for health apps).

Automate Google Play Store updates