Description

Runway OTA hotfixes use a two-digit patch (e.g. 7.76.01) so CI can distinguish OTA hotfixes from native hotfixes (7.76.1). That form is not valid SemVer, so @metamask/auto-changelog fails when the release changelog workflow passes it through unchanged.

This PR:

• Detects OTA hotfixes when the patch segment has exactly two digits (resolve-bases in create-release-pr.yml) and sets is_ota.

• Skips native semver / build-version bump for OTA: generate-build-version is skipped; create-release-pr still runs using always() and explicit job-result checks so skipped dependents do not block the job.

• Bumps only OTA_VERSION in app/constants/ota.ts via bump-ota-version-constants.sh, commits and pushes the release branch, and creates a draft PR to stable when none exists. A prior gh pr list check avoids double-bumping on retries.

• Changelog: run-update-release-changelog-mobile.sh calls github-tools update-release-changelog.sh with a SemVer prerelease mapping X.Y.AB → X.Y.A-ota.B so headers stay valid for auto-changelog. Comparison URLs are post-processed on release-changelog/ so GitHub compare links use the real Runway tag (e.g. v7.76.01) instead of a non-existent v7.76.0-ota.1.

• Wires update-release-changelog.yml and the OTA path in create-release-pr.yml through that wrapper (with github-tools checkout + yarn install + script).

• Hardens runway-ota-build-core.yml by parsing OTA_VERSION from the export line instead of a fixed line number (comment length changes).

• Documents the convention in auto-create-release-pr.yml comments and app/constants/ota.ts JSDoc; adjusts Runway workflow comments that referenced a specific line.

Testing:
OTA hotfix 7.77.01 ✅
release PR: #28478
changelog PR: https://github.com/MetaMask/metamask-mobile/pull/28477/changes

Binary hotfix 7.77.3 ✅
release PR: #28485
changelog PR: #28484

OTA hotfix 7.77.31 ✅
release PR: #28488
changelog PR: https://github.com/MetaMask/metamask-mobile/pull/28487/changes

Changelog

CHANGELOG entry: ci: include OTA version bump when creating a new release branch

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.