Write out the entire release process in steps

This commit is contained in:
Caleb Jasik 2025-02-04 13:31:31 -06:00
parent 0112d7a607
commit 82c8c55859
No known key found for this signature in database

View file

@ -43,11 +43,12 @@ In Android Studio, set the line length using Preferences → Editor → Code Sty
# Prerelease # Prerelease
Push a git tag `v#.#.#-##`, e.g. `v0.5.2-0`, and `.github/release.yml` will build a draft release and publish it to iOS TestFlight and Android internal track. Push a git tag `v#.#.#-##`, e.g. `v0.5.1-0`, and `.github/release.yml` will build a draft release and publish it to iOS TestFlight and Android internal track.
# Release # Release
We manually promote a prerelease build from TestFlight and Android internal track to the public app stores, and then mark the associated draft release as published, removing the `-##` from it, ending with a release in the format `v#.#.#`, e.g. `v0.5.2`. 1. Manually promote a prerelease build from TestFlight and Android internal track to the corresponding public app stores.
2. Mark the associated draft release as published, removing the `-##` from it, ending with a release in the format `v#.#.#`, e.g. `v0.5.1`.
Additionally, we should add the notable changes to the app to the release details. 3. Remove the old draft releases that will never be published.
4. Add the notable changes to the app to the release summary, e.g.: <https://github.com/DefinedNet/mobile_nebula/releases/tag/v0.5.1>.