@Manoj I think it’s good you budget resources to validate OTA updates - but as you go that route and ask users to manually change major versions, please prioritize updating the Seedvault backup in the existing images, it’s now many years old - lots of disadvantages before A13 were addressed since.
- basically, a developer just places a newly built seedvault apk from android13/android14 branches from upstream in t/u branches at SeedVault · main · e / os / android_prebuilts_prebuiltapks_lfs · GitLab - (though I see there’s no longer the major version distinction)
- the one ticket still open on Seedvault to get attention: Allow restore of a SeedVault backup (#7639) · Issues · e / Backlog · GitLab - but would read “update Seedvault”
Regular users can then have a more robust upgrade experience and a fallback/restore path in case of failure. If I know that I get the attention of a developer to merge it in time I can make a PR. But for the git-lfs repo I think you won’t accept binary apks built outside your infra.