ci(build): convert build.yml to workflow_call-only and add Build Android wrapper

[tommasini]

Summary

• Adds a new build-android.yml (Build Android) workflow that mirrors the structure of build-and-upload-to-testflight.yml but for Android APK/AAB: creates an ephemeral build branch, bumps the version via build.yml, builds the Android artifacts, and cleans up the branch. No upload step.
• Adds runtime validate-inputs guards to both workflows to enforce the same closed sets that workflow_dispatch previously expressed via type: choice (since workflow_call inputs do not support type: choice).

Changes

build-android.yml (new)

• workflow_call + workflow_dispatch triggers
• Inputs: source_branch (required, "Branch, tag, or SHA to build"), environment (exp/beta/rc), upload_to_sentry, runner_provider
• Outputs: build_branch, built_commit_sha, semantic_version, android_version_code
• Jobs: validate-inputs → prepare-build-branch (create-build-branch.yml) → build (build.yml, platform: android) → cleanup-build-branch
• APK/AAB artifacts are uploaded by the existing Upload Android * steps inside build.yml; no new artifact handling needed in the wrapper

Callers unaffected

All existing callers of build.yml (nightly-build.yml, runway-rc-builds.yml, runway-production-builds.yml, expo-dev-build.yml, auto-rc-ota-build-core.yml, build-android-upload-to-browserstack.yml, build-ios-upload-to-browserstack.yml, build-and-upload-to-testflight.yml) continue to work unchanged — they all use workflow_call.

Manual testing

• Trigger Build Android workflow manually from GitHub Actions UI with a valid branch and environment: rc
• Verify validate-inputs fails fast with a clear error if an invalid environment or build_name is passed programmatically

Made with Cursor

---

Note

Medium Risk
Changes CI workflow entrypoints and adds new runtime validation, which could break manual builds or callers if inputs/keys don’t match builds.yml or if yq isn’t available on runners.

Overview
Adds a new Build Android workflow (build-android.yml) that can be manually triggered or called by other workflows to create an ephemeral build branch, run the existing reusable build.yml for Android (main-exp/beta/rc), and then delete the temporary branch.

Updates build.yml to be workflow_call-only by removing its workflow_dispatch trigger and adding a fast-fail validate-inputs job that enforces allowed platform/runner_provider values and requires build_name to exist in builds.yml before running version bump/build steps.

^{Reviewed by Cursor Bugbot for commit 18b9790. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

E2E Test Selection:
The two changed files are purely CI/build infrastructure changes with no impact on application code or E2E test infrastructure:

1. .github/workflows/build-android.yml (NEW FILE): A new reusable workflow that orchestrates Android-only builds. It creates a temp branch, bumps the version via build.yml, builds the Android APK/AAB, and cleans up the branch. This mirrors the iOS build-and-upload-to-testflight.yml pattern but for Android without the upload step. This is purely a CI pipeline addition.

2. .github/workflows/build.yml (MODIFIED): Changes include:

   • Removing the workflow_dispatch trigger (manual dispatch removed from this workflow)
   • Adding a new validate-inputs job that enforces allowed values for build_name, platform, and runner_provider at runtime using shell case statements and yq to parse builds.yml
   • Adding descriptive comments to input parameters
   • Making update-build-version depend on the new validate-inputs job

Neither change touches: app source code, test files, E2E test infrastructure (tests/ directory), page objects, fixtures, or any component that would affect Detox test execution. These are build pipeline improvements that add input validation and a new Android build workflow. No E2E tests need to run to validate these changes.

Performance Test Selection:
The changes are purely CI/build workflow modifications with no impact on app code, rendering, state management, or any component that could affect performance. No performance tests are warranted.

View GitHub Actions results

[Cal-L]

LGTM

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud