Skip to content

chore: Add skip build to upload to testflight#28293

Closed
weitingsun wants to merge 2 commits intomainfrom
wsun/add-skip-build-to-upload-to-testflight
Closed

chore: Add skip build to upload to testflight#28293
weitingsun wants to merge 2 commits intomainfrom
wsun/add-skip-build-to-upload-to-testflight

Conversation

@weitingsun
Copy link
Copy Markdown
Contributor

@weitingsun weitingsun commented Apr 1, 2026

Description

Changelog

CHANGELOG entry:

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

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 iOS TestFlight upload pipeline and artifact naming/parameterization in GitHub Actions, which can break release automation if inputs/artifacts don’t line up. No production app code changes, but failures would block builds/uploads.

Overview
Refactors Runway’s iOS TestFlight step to reuse the dedicated upload-to-testflight.yml workflow, removing the previously inlined checkout/upload steps and summary job from runway-ota-build-core.yml.

Extends upload-to-testflight.yml with skip_build, build_name, custom summary title, and external distribution toggle, and updates job gating/branch cleanup so it can either build-and-upload or upload an existing IPA artifact (ios-ipa-{build_name}) within the same run.

Written by Cursor Bugbot for commit 0c1aa2b. This will update automatically on new commits. Configure here.

@weitingsun weitingsun requested review from a team as code owners April 1, 2026 20:40
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 1, 2026

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.

@metamaskbot metamaskbot added the team-mobile-platform Mobile Platform team label Apr 1, 2026
@github-actions github-actions bot added size-M risk-low Low testing needed · Low bug introduction risk labels Apr 1, 2026
@github-actions github-actions bot added risk-low Low testing needed · Low bug introduction risk and removed risk-low Low testing needed · Low bug introduction risk labels Apr 1, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 1, 2026

🔍 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:
Both changed files are GitHub Actions CI/CD workflow files related to iOS TestFlight upload pipeline:

  1. runway-ota-build-core.yml: Refactored to remove inline TestFlight upload logic (removed testflight-upload-summary and upload-ios-testflight jobs) and replaced with a call to the reusable upload-to-testflight.yml workflow. This is purely a CI pipeline restructuring.

  2. upload-to-testflight.yml: Enhanced the reusable workflow with a skip_build input flag (to allow callers that already have an IPA artifact to skip the build step), added build_name, summary_title, and distribute_external inputs, and updated conditional job execution logic accordingly.

These changes are entirely within the CI/CD infrastructure for building and distributing iOS builds to TestFlight. They do not touch:

  • Any application source code
  • Any E2E test files or test infrastructure (Detox, fixtures, page objects)
  • Any app configuration (package.json, metro.config.js, babel.config.js)
  • Any controllers, Engine, or core modules
  • Any UI components or navigation

No E2E tests are needed to validate these changes. The changes only affect how iOS builds are uploaded to TestFlight, which is a deployment concern unrelated to app functionality or test execution.

Performance Test Selection:
These are purely CI/CD workflow changes with no impact on app code, rendering, data loading, or any other aspect that could affect performance. No performance tests are warranted.

View GitHub Actions results

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Fix All in Cursor

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

build_name: ${{ inputs.build_name }}
source_branch: ${{ inputs.source_branch || github.ref_name }}
summary_title: ${{ inputs.ios_testflight_summary_title }}
secrets: inherit
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing distribute_external: false flips distribution behavior

High Severity

The old inline job explicitly passed "false" for distribute_external when calling upload-to-testflight.sh. The new reusable workflow call omits the distribute_external input, which defaults to true in upload-to-testflight.yml. This silently changes behavior from "upload only" to "distribute to external testers" for iOS RC and Production Runway builds. The workflow input description itself notes that false "avoids App Manager role requirement," so this change may also cause permission failures.

Additional Locations (1)
Fix in Cursor Fix in Web

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 1, 2026

@weitingsun weitingsun closed this Apr 2, 2026
@weitingsun weitingsun deleted the wsun/add-skip-build-to-upload-to-testflight branch April 2, 2026 01:26
@github-actions github-actions bot locked and limited conversation to collaborators Apr 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

risk-low Low testing needed · Low bug introduction risk size-M team-mobile-platform Mobile Platform team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants