chore: Add group to upload testflight workflow and show build number

[Cal-L]

Description

This change adds Acolad Product QA to the upload to test flight workflow. It also displays the build number to better help users better identify the uploaded build

Changelog

CHANGELOG entry:

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MCWP-447

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

Low Risk
Low risk CI-only change limited to GitHub Actions workflow wiring and summary output formatting, with no runtime/app code impact. Main risk is miswired outputs causing missing build numbers in downstream workflows.

Overview
The reusable build.yml workflow now exports a build_version output (native build number from the version-bump) and threads it through the prepare job outputs.

The upload-to-testflight.yml workflow adds the Acolad Product QA TestFlight group option and updates the step summary to display the build number via needs.build.outputs.build_version (instead of parsing Android versionCode), with minor renaming/formatting of the summary job.

^{Written by Cursor Bugbot for commit 290762c. 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:
The two changed files are purely CI/CD workflow files with no impact on app source code, E2E test infrastructure, or app behavior:

1. .github/workflows/build.yml: Adds a build_version output to the workflow_call interface so callers can consume the native build number. Also passes this value through to the prepare job. This is a plumbing change to expose an existing value as a workflow output — no app code is affected.

2. .github/workflows/upload-to-testflight.yml:

   • Adds 'Acolad Product QA' as a new allowed TestFlight distribution group
   • Renames the summary job name
   • Refactors the step summary to use needs.build.outputs.build_version (the new output from build.yml) instead of parsing android/app/build.gradle directly
   • Minor formatting changes to the summary table

Neither file touches: app source code, test files, E2E test page objects, Detox configuration, navigation, controllers, or any shared component. These are purely CI/CD pipeline changes affecting build distribution and summary reporting. No E2E tests need to run to validate these changes.

Performance Test Selection:
No app source code changes were made. The changes are limited to CI/CD workflow files affecting build version propagation and TestFlight group configuration. There is no impact on app rendering, data loading, startup, or any other performance-sensitive area.

View GitHub Actions results

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Duplicate workflow ref in summary table

Low Severity

upload-to-testflight.yml writes the Workflow ref row twice in the same summary table. This introduces redundant output and inconsistent formatting for the same field, which makes the upload summary noisier and harder to scan when validating release metadata.

 

[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