Problem
There is no automated EAS build pipeline. Every release requires the maintainer to manually run eas build --platform android --profile production and upload the APK, which delays releases and risks human error.
Context
Releases gated by manual steps don't happen on schedule. Automating production builds on v* tag push means tagging a commit produces a downloadable APK with zero further action.
Before Starting
Read these context files first:
- context/architecture-context.md
- context/code-standards.md
- context/progress-tracker.md
- eas.json
What To Build
- Create
.github/workflows/eas-build.yml.
- Trigger:
push with tags: ['v*'].
- Job
production-android: ubuntu-latest, Node 20.
- Steps: checkout → setup-node →
npm ci → install eas-cli → eas build --platform android --profile production --non-interactive --no-wait.
- Auth via
EXPO_TOKEN secret (must be added in repo settings — document in workflow comment).
- After job, run
eas build:list --json and download APK, upload as release asset via actions/upload-release-asset.
Files To Touch
.github/workflows/eas-build.yml
eas.json (verify production profile exists)
README.md (release process section)
Acceptance Criteria
Mandatory Checks Before PR
Problem
There is no automated EAS build pipeline. Every release requires the maintainer to manually run
eas build --platform android --profile productionand upload the APK, which delays releases and risks human error.Context
Releases gated by manual steps don't happen on schedule. Automating production builds on
v*tag push means tagging a commit produces a downloadable APK with zero further action.Before Starting
Read these context files first:
What To Build
.github/workflows/eas-build.yml.pushwithtags: ['v*'].production-android: ubuntu-latest, Node 20.npm ci→ installeas-cli→eas build --platform android --profile production --non-interactive --no-wait.EXPO_TOKENsecret (must be added in repo settings — document in workflow comment).eas build:list --jsonand download APK, upload as release asset viaactions/upload-release-asset.Files To Touch
.github/workflows/eas-build.ymleas.json(verify production profile exists)README.md(release process section)Acceptance Criteria
v0.1.0triggers an EAS production buildEXPO_TOKENsecret is documented as requiredbuildType: apkoraabMandatory Checks Before PR