Skip to content

release.md

Latest commit

 

History

History
48 lines (32 loc) · 2.06 KB

release.md

File metadata and controls

48 lines (32 loc) · 2.06 KB
Raw

Release

GitHub APK releases and Play Store releases are separate paths.

Before any release, make sure the app builds locally. Set up local build prerequisites as described in develop.md.

Pre-release build check

Restore fallback rates and icons as described in develop.md.

Run the local checks:

./gradlew ktlintCheck lint assembleDebug

GitHub APK release

Use this path to publish APK artifacts through GitHub Releases.

  1. Update versionCode and versionName in app/build.gradle.kts.
  2. Push the release commit.
  3. Create and push a version tag:
git tag vX.Y.Z
git push origin vX.Y.Z

Pushing the tag triggers release.yml; see workflows.md for what that workflow does.

After the GitHub Release is created, review or add GitHub Release notes as described in publication.md.

Play Store release

Use this path for the production Play Store release. Play Store publishing is done manually from Android Studio on the release manager's machine.

  1. Update versionCode and versionName in app/build.gradle.kts.
  2. Put keystore.jks in the project root from the secret storage.
  3. Put the production app/google-services.json from the secret storage.
  4. Restore bundled fallback rates and icons as described in develop.md.
  5. Publish the GitHub APK release as described above and use it as a pre-Play-Store verification step.
  6. Open the project in Android Studio and create the signed Google Play release artifact using the production signing/config files.
  7. Prepare release notes as described in publication.md.
  8. Upload the generated Play Store artifact through Google Play Console and include the release notes.
  9. Finish listing updates, website updates, and announcements as described in publication.md.

Do not commit keystore.jks, production app/google-services.json, fallback rates, updatedAt, generated crypto icons, or generated release artifacts.