K2GO-90 chore(release): v0.8.0-beta, the first release under the new identity - #533
Merged
Conversation
…identity versionCode 61 and versionName v0.8.0-beta. The OTA note is written for the only audience that can see it: nobody runs a version below 61 under the new identity, so the update dialog carrying this text reaches exactly the devices still on the old identifier — where the update downloads and is then refused, because the signature check will not install an APK signed by a different key. Rather than leave those users with a failed download, the note gives them the path that works: back up, remove, install by hand, restore. Backups made by the old app restore into the new one; that was verified on device, not assumed.
Brings in the manifest rename and the staged-APK name so the release carries them.Merge remote-tracking branch 'origin/main' into chore/K2GO-90-release-v0.8.0
…ucket rootfs_sizes.csv and module_sizes.csv still carried August figures measured against the retired host. They are what the app shows when it cannot reach the network, so releasing with them stale means quoting sizes for artifacts that no longer exist anywhere.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the tag.
versionCode61,versionNamev0.8.0-beta, the OTA note, and the offline sizetables refreshed against the bucket that actually holds the artifacts.
The OTA note is written for the only audience that can read it
Nobody runs a version below 61 under the new identity, so the update dialog carrying this text
reaches exactly the devices still on
org.iiab.controller. Those devices will see the update —they poll the same
update.jsonand 61 > 60 — download it, and then have it refused, because thesignature check will not install an APK signed by a different key.
Rather than leave them with a failed download and no explanation, the note gives them the path that
works: back up, remove the old app, install by hand, restore. That sequence is verified, not
assumed — backups made by the old app restore into the new one, tested on device today.
The size tables
rootfs_sizes.csvandmodule_sizes.csvstill carried August figures measured against the retiredhost. They are the offline fallback the app shows when it cannot reach the network, so releasing
with them stale means quoting sizes for artifacts that no longer exist anywhere. Regenerated from
k2go-rootfs and checked digit-for-digit against what the bucket serves.
What tagging this does beyond publishing
The release workflow uploads
update.jsonas its last step. That file has been returning 404 sincethe APK bucket migration, so this tag also brings the OTA back — the same run, no separate action.
Not here
No version bump for the rootfs images: the tier images are published by their own bake and are
unrelated to the app's version. The Firebase App Distribution permission issue is being handled
separately and does not touch this pipeline — that workflow has no distribution step.