CHT Core Framework > Guides > Android > Publishing
Instructions for Publishing Android Apps
All Medic’s android projects automatically build, sign, and release builds via Github Actions or Travis. The following guide applies to any of these apps, although the last 2 are in maintenance mode (links pointing to the release sections):
master
. You can also create an alpha release from a feature branch, to provide the needed .apk
files to the QA team.v
and ending with the alpha version, e.g. git tag v1.2.3-alpha.1
and push the tag to GitHub (git push --tags
). For features branches, you can add the name of the branch or whatever keyword helps to identify the the release, e.g. v1.2.3-alpha.dark-theme.4
.v<major>.<minor>.<patch>
.medicmobilegamma
and unbranded
) must be published in the Play Store.Only CHT Android
The new flavor should have branched off from the last stable release in CHT Android repository, for example, if the latest stable release is v1.2.3
and the branch name is v1.2.3-new-brand
, then check out the tag and create a branch using the following command:
git checkout v1.2.3 -b v1.2.3-new-brand
Add the flavor and make a pull request to the release branch. Once it has been approved, squash and merge
the pull request, tag the commit with the same version as the last one and add a number suffix separated with a dash character (-
), e.g. if the last version was v1.2.3
, tag it as v1.2.3-1
. In this case, it’s not necessary to publish again the reference apps in Play Store or to announce the release in the forum, if not relevant.
Finally, make sure this commit is backported to the repository’s main branch.
Instructions for Publishing Android Apps
Branding the CHT Android with “Flavors” Apps
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.