Skip to content

Commit dff785f

Browse files
docs: add "watch the run" step to release cycle (#2230)
The old release flow ended at "create the GitHub release", which is what triggers play-release.yml but isn't itself the moment the update reaches users. If the Play upload fails after the release publishes, the release exists but the AAB never lands — and the maintainer can step away thinking the work is done. Step 5 now says to watch the Play Release run with gh run watch until it succeeds. The prior step 5 ("Tag automatically created during release process") was a note, not an action; folded it into step 4 as a parenthetical. Co-authored-by: Owen McGirr <o.a.mcgirr@gmail.com>
1 parent fa90457 commit dff785f

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

AGENTS.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -162,8 +162,8 @@ Complete release process:
162162
1. Bump version in `app/build.gradle.kts` (versionName field)
163163
2. Commit and push the version bump
164164
3. Close current milestone in GitHub
165-
4. Create GitHub release with auto-generated release notes
166-
5. Tag automatically created during release process
165+
4. Create GitHub release with auto-generated release notes (tag auto-created)
166+
5. Watch the Play Release workflow run with `gh run watch` and do not close the terminal until it reports success — a failure here means the signed AAB never reached Google Play, so the GitHub release exists but no update rolls out to users. Investigate and rerun before walking away.
167167

168168
### Version Bumps
169169
- Update version in build.gradle.kts

0 commit comments

Comments
 (0)