Document

.github/workflows/auth-release.yml

@@ -18,7 +18,10 @@ name: "Release (auth)"
 # We use a suffix like `-test` to indicate that these are test tags, and that
 # they belong to a pre-release.
 #
-# Once the test is done, also delete the tag please.
+# If you need to do multiple tests, add a +x at the end of the tag. e.g.
+# `auth-v1.2.3-test+1`.
+#
+# Once the testing is done, also delete the tag(s) please.
 
 on:
     push:

auth/docs/release.md

@@ -2,11 +2,19 @@
 
 1. Create a PR to bump up the version number in `pubspec.yaml`.
 
-2. Once that is merged, tag main. This'll trigger the
-   [workflow](.github/workflows/ci.yml) to (a) create a new GitHub release with
-   the independently distributed APK, and (b) build and upload a release to
-   Google Play.
+2. Once that is merged, tag main and push the tag. This'll trigger a GitHub
+   workflow that:
 
-3. Xcode Cloud has already been configured and will automatically build and
-   release to TestFlight when step 1 was merged to main (you can see logs under
-   the PR checks).
+   a. Creates a new draft GitHub release and attaches all the build artifacts to
+      it (mobile APKs and various desktop packages)
+
+   b. Creates a new release in the internal track on Play Store.
+
+3. (TODO(MR): Fix this after the monorepo move) Xcode Cloud has already been
+   configured and will automatically build and release to TestFlight when step 1
+   was merged to main (you can see logs under the PR checks).
+
+If you want to make changes to the workflow itself, or test it out, you can push
+a tag like `auth-v1.2.3-test` (where v1.2.3 is the next expected version that'll
+go out). For more details, see the comments on top of the [auth-release
+workflow](.github/workflows/auth-release.yml).