Description

In the current workflow, the OTA PR needs to point to a base that is the same as the branch that we are applying the OTA to. However, this does not work because when we have a release branch, since the base is always stable so we will need to change the base branch whenever we run OTA update.

In this PR:

• Get rid of hash commit input. We don't really need it because we will remove the approval if a new commit is pushed and we will always use the latest commit
• We get the latest commit hash in the OTA PR and output it in the workflow
• Remove the restriction on the OTA base branch. In the OTA PR, it shouldn't matter which base branch it's pointing to. We will compare the fingerprint to the actual release tag that the OTA is applying (which is one of the inputs when triggering the workflow)

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

Changelog

CHANGELOG entry: Removed OTA workflow commit hash input

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.