Skip to content

[34] Add EAS production build workflow #10

@EmeditWeb

Description

@EmeditWeb

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

  1. Create .github/workflows/eas-build.yml.
  2. Trigger: push with tags: ['v*'].
  3. Job production-android: ubuntu-latest, Node 20.
  4. Steps: checkout → setup-node → npm ci → install eas-clieas build --platform android --profile production --non-interactive --no-wait.
  5. Auth via EXPO_TOKEN secret (must be added in repo settings — document in workflow comment).
  6. 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

  • Pushing tag v0.1.0 triggers an EAS production build
  • APK is attached to the corresponding GitHub release
  • EXPO_TOKEN secret is documented as required
  • No secrets leaked in logs
  • eas.json has a production profile with buildType: apk or aab
  • Release process documented in README

Mandatory Checks Before PR

  • CI passes on a test PR before merging
  • Zero secrets committed to the repo
  • context/progress-tracker.md updated

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions