2023-01-28 10:01:24 +00:00
|
|
|
# Releases
|
|
|
|
|
|
2024-03-05 14:07:51 +00:00
|
|
|
Create a PR to bump up the version in `pubspec.yaml`. Once that is merged, tag
|
|
|
|
|
main, and push the tag.
|
2023-01-28 10:01:24 +00:00
|
|
|
|
2024-03-05 14:07:51 +00:00
|
|
|
```sh
|
|
|
|
|
git tag auth-v1.2.3
|
|
|
|
|
git push origin auth-v1.2.3
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
This'll trigger a GitHub workflow that:
|
2024-03-05 04:27:19 +00:00
|
|
|
|
2024-03-05 06:43:03 +00:00
|
|
|
* Creates a new draft GitHub release and attaches all the build artifacts to it
|
|
|
|
|
(mobile APKs and various desktop packages),
|
2024-03-05 04:27:19 +00:00
|
|
|
|
2024-03-05 06:43:03 +00:00
|
|
|
* Creates a new release in the internal track on Play Store.
|
2024-03-05 04:27:19 +00:00
|
|
|
|
2024-03-05 14:07:51 +00:00
|
|
|
Once the workflow completes, go to the draft GitHub release that was created.
|
|
|
|
|
Set "Previous tag" to the last release of auth and press "Generate release
|
|
|
|
|
notes". The generated release note will contain all PRs and new contributors
|
|
|
|
|
from all the releases in the monorepo, so you'll need to filter them to keep
|
|
|
|
|
only the things that relate to the auth.
|
