Document automated releases
This commit is contained in:
parent
ca809a0e0b
commit
7666c4e053
2 changed files with 15 additions and 0 deletions
|
@ -88,6 +88,9 @@ tokens has been documented [here](architecture/README.md).
|
|||
4. For Android, run `flutter build apk --release --flavor independent`
|
||||
5. For iOS, run `flutter build ios`
|
||||
|
||||
For maintainers, there is [additional documentation](RELEASES.md) on
|
||||
automatically publishing the main branch to App store, Play store and GitHub
|
||||
releases.
|
||||
|
||||
## 🙋♂️ Support
|
||||
|
||||
|
|
12
RELEASES.md
Normal file
12
RELEASES.md
Normal file
|
@ -0,0 +1,12 @@
|
|||
# Releases
|
||||
|
||||
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.
|
||||
|
||||
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).
|
Loading…
Reference in a new issue