Description

The trigger-ota job mixed shell steps with a reusable workflow (uses: ./.github/workflows/push-eas-update.yml). In GitHub Actions, a job must either define steps: or call another workflow with job-level uses:, not both.
This splits that into:

1. validate-ota-pr — Validates a PR number exists before OTA (same guard as before).
2. trigger-ota — Only calls push-eas-update.yml, with secrets: inherit for caller secrets.
   create-ota-production-tag now sets tag_name from needs.decide.outputs.ota_version (same value the old release_tag step echoed). It still needs: trigger-ota so tagging runs only after the OTA workflow finishes.

successful workflow run: https://github.com/MetaMask/metamask-mobile/actions/runs/23923283109

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.