chore: use push EAS directly

[weitingsun]

Description

• Use push EAS update in the Runway workflow directly
• Fix PR number null issue

Changelog

CHANGELOG entry:null

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Medium Risk
Changes the release/OTA GitHub Actions orchestration by switching from API dispatch to a reusable workflow and tweaking PR-number resolution; mistakes here could block OTA publishing or target the wrong ref.

Overview
Updates the OTA publishing pipeline to call push-eas-update.yml as a reusable workflow (workflow_call) instead of dispatching it via actions/github-script, simplifying runway-ota-build-core.yml.

Also fixes PR-number discovery to treat gh pr list returning null as empty (avoiding false positives), and updates CODEOWNERS to include the new build-and-upload-to-testflight.yml workflow under @MetaMask/mobile-admins.

^{Written by Cursor Bugbot for commit 633c2ac. This will update automatically on new commits. 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: 97%

click to see 🤖 AI reasoning details

E2E Test Selection:
All three changed files are purely CI/CD infrastructure:

1. .github/CODEOWNERS: Adds build-and-upload-to-testflight.yml to @MetaMask/mobile-admins ownership. Pure administrative metadata change with zero impact on app code or tests.

2. .github/workflows/push-eas-update.yml: Adds a workflow_call trigger block to make this workflow reusable by other workflows. No changes to the actual workflow steps or app build logic.

3. .github/workflows/runway-ota-build-core.yml: Two changes:

   • Bug fix: jq '.[0].number // empty' to normalize null output when PR list is empty (prevents literal "null" string being used as PR number).
   • Refactor: Replaces actions/github-script@v7 + createWorkflowDispatch API call with a direct uses: ./.github/workflows/push-eas-update.yml workflow_call invocation, leveraging the new reusable workflow trigger.

None of these changes touch application source code, test infrastructure (Detox/WDIO), controllers, UI components, navigation, or any code path exercised by E2E tests. These are purely GitHub Actions CI/CD pipeline improvements. No E2E tests need to run to validate these changes.

Performance Test Selection:
No application code was changed. These are purely CI/CD workflow and CODEOWNERS file changes with no impact on app rendering, data loading, state management, or any other performance-sensitive code paths.

View GitHub Actions results

[Cal-L]

LGTM