| id | AgDR-0005 |
|---|---|
| timestamp | 2026-01-31 09:30:00 UTC |
| agent | claude-code |
| model | claude-opus-4-5 |
| trigger | user-prompt |
| status | executed |
In the context of needing to distribute Android APKs directly, facing the need for automated versioning and release management, I decided to use GitHub Actions with manual workflow_dispatch to achieve controlled releases with automatic version bumping, accepting the dependency on GitHub's infrastructure.
- Distributing APKs directly (not Play Store initially)
- Need automatic version bumping (semantic versioning)
- Need signed releases for Android installation
- GitHub already hosts the repository
| Option | Pros | Cons |
|---|---|---|
| GitHub Actions (manual dispatch) | Native to GitHub, easy secrets management, manual control over releases | Locked to GitHub ecosystem |
| GitHub Actions (tag-triggered) | Fully automated on tag push | Less control, easy to trigger accidentally |
| Fastlane | Industry standard, rich Android tooling | Additional dependency, more config |
| Local build script | Simple, no CI dependency | No automation, manual secrets handling |
Chosen: GitHub Actions with workflow_dispatch, because it provides the right balance of automation (version bumping, signing, release creation) with control (manual trigger prevents accidental releases).
- Releases are triggered manually via GitHub UI or CLI
- Version is automatically bumped based on selected type (patch/minor/major)
- APK is signed and attached to GitHub Release
- Changelog is auto-generated from commits
- Requires GitHub secrets for keystore credentials