release: Post release artifacts on GitHub, too

Fixes: #640

Author: gnprice

docs/changelog.md

@@ -16,7 +16,10 @@
 * The tree includes configuration for Android Studio / IntelliJ,
   which should help exclude extraneous results from search. (PR #637)
 
-Resolved: #548, #620, #538, #612, #356, #309, #634, PR #680
+* Starting with this release, we post releases on GitHub, as well as
+  on Google Play and TestFlight.
+
+Resolved: #548, #620, #538, #612, #356, #309, #634, PR #680, #640
 
 
 ## 0.0.14 (2024-04-25)

docs/release.md

@@ -29,13 +29,13 @@
   ../mobile/tools/checkout-keystore
   ```
 
-* Build an Android App Bundle, signed:
+* Build both an Android App Bundle (AAB) and an APK, signed:
 
   ```
-  flutter build appbundle -Psigned
+  flutter build appbundle -Psigned && flutter build apk -Psigned
   ```
 
-* Upload to the "Zulip (Flutter beta)" app on the Play Console,
+* Upload the AAB to the "Zulip (Flutter beta)" app on the Play Console,
   at [Release > Testing > Internal testing][play-internaltesting],
   using the "Create new release" button there.
 
@@ -98,6 +98,22 @@
   * Confirm and send to Google for review.
 
 
+* Android via GitHub:
+
+  * Create a GitHub release, named the same as the tag.
+
+  * For the release notes, use `tools/format-changelog notes`,
+    and fix formatting as needed.
+
+    * The hashes printed at the bottom are based on the files found at
+      the usual build-output locations.  Those should be the same
+      files you upload.
+
+  * Upload both the AAB and the APK.
+
+  * Check the box "This is a pre-release".
+
+
 * iOS via TestFlight:
 
   * After the build reaches alpha, you can add it to TestFlight so it

tools/format-changelog

@@ -47,6 +47,7 @@ cmd_user() {
 show_hash() {
     local artifacts filename output hash basename
     artifacts=(
+        "${root}"/build/app/outputs/flutter-apk/app-release.apk
         "${root}"/build/app/outputs/bundle/release/app-release.aab
     )
     echo "sha256sum -c <<EOF"