Skip to content

ci(eas): build Android and iOS on every pull request to main - #29

Merged
dsatpm merged 1 commit into
mainfrom
dsatpm/eas-pr-builds-80e04f4d
Oct 10, 2026
Merged

dsatpm merged 1 commit into
mainfrom
dsatpm/eas-pr-builds-80e04f4d

Conversation

@dsatpm

@dsatpm dsatpm commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

Builds Android and iOS on EAS for every pull request to main.

What changed

  • .eas/workflows/pr-builds.yml: two build jobs that run on pull_request to main. A new push to the branch cancels the run already in progress.
  • eas.json: a new pr profile, built in the Release configuration so prebuild, the config plugins and the native compile run the same way they do for store builds.
    • Android: APK with withoutCredentials: true, signed with the template's debug keystore.
    • iOS: simulator: true.
    • Neither needs signing credentials. That matters because every iOS production build so far has errored at "Resolve build configuration".
  • tests/easWorkflows.test.ts: checks that every profile a workflow names exists in eas.json, and that the pr profile stays credential-free.

How it was tested

  • npx eas-cli workflow:validate .eas/workflows/pr-builds.yml reports "Workflow configuration YAML is valid."
  • npx jest tests/easWorkflows.test.ts passes 4/4; npm run typecheck and npm run lint are clean.
  • Live run: this PR is the first trigger. It only runs if the GitHub repo is connected to the Expo project (expo.dev > project > GitHub).

Cost

Each PR push starts 2 EAS builds against the plan's build minutes.

🤖 Generated with Claude Code

.eas/workflows/pr-builds.yml runs two EAS build jobs on pull_request to main,
cancelling an in-progress run when the branch gets a new push. They use a new
"pr" profile: an Android APK with withoutCredentials (signed by the template
debug keystore) and an iOS simulator build, so neither needs signing
credentials. Release configuration, so prebuild, config plugins and the native
compile are exercised as they ship.

tests/easWorkflows.test.ts checks every workflow profile exists in eas.json
and pins the pr profile to credential-free settings. `eas workflow:validate`
reports the file valid.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dsatpm
dsatpm merged commit 2f5ada5 into main Oct 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant