Repository navigation
K2GO-452 feat(release): define the v1.1.0 release (version bump + OTA notes) - #636
Merged
Merged
Conversation
… notes) versionCode 63 -> 64, versionName v1.0.0 -> v1.1.0; add the v1.1.0 OTA notes entry (its header must match the release tag). Maintenance release carrying the fixes merged since v1.0.0. No beta cleanup or workflow change (one-time at 1.0).
The update dialog (BrandDialog) has no scroll, so a long note can push the buttons off a small screen. Trim to 3 lines (the file's own 1-3 line rule).
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.
Prepare the v1.1.0 maintenance release. Models the v1.0.0 release (K2GO-431), minus
the one-time beta cleanup.
the tag; kept to 3 lines, since the update dialog does not scroll).
Coordination: merge this last, then tag v1.1.0. The release workflow then builds the
standard + fdroid APKs and the Play AAB, uploads all to R2, and publishes the OTA
update.json (standard only).