The build step minted a fresh keystore inside the checkout on every run, so each CI release was signed with a different key. Upgrading from any previous release then failed with a signature conflict (INSTALL_FAILED_UPDATE_INCOMPATIBLE) — and with allowBackup=false, the only workaround was uninstalling, which destroys the user's notes. The keystore is now minted once in /tmp/gitea-runner-work (the same persistent cache that already holds the JDK and Android SDK) and copied into the checkout before building. Every release from now on shares one signing key, so in-place upgrades work. Only a runner-host rebuild would mint a new key (breaking exactly one upgrade). Note: v0.3.7.0 was signed with an ephemeral key that no longer exists, so the v0.3.7.0 -> v0.3.7.1 upgrade still requires a one-time uninstall (export a backup first).