chore: cherry pick 28423#28540
Conversation
|
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. |
|
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection:
None of these changes:
The changes are purely about how RC builds are triggered, how build metadata is read, and how Slack/PR notifications are posted after builds complete. Running E2E tests would provide no validation value for these changes. Performance Test Selection: |



Description
cherry-pick #28423
Changelog
CHANGELOG entry:
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Medium Risk
Reworks release-candidate build orchestration and notification plumbing across multiple GitHub Actions workflows; misconfiguration could cause missing/incorrect RC builds, version bumps, or Slack/PR announcements.
Overview
Auto RC builds are refactored to run through the reusable
runway-ota-build-core.yml: iOS RC runs first (and performs the version bump), then Android RC runs withskip_version_bump, replacing the prior inline Bitrise-trigger script approach.Adds a reusable
slack-rc-notification.ymlworkflow and a newscripts/get-build-metadata.shto read semver + iOS/Android build numbers from the checked-out branch; PR comments and Slack messages now use these values and fall back to linking the GitHub Actions run when no Android public install URL is available.Removes the manual
build-rc-create.ymlworkflow, updates Runway RC workflows to post Slack notifications after success, and adjustsbuild.yml/metadata emission to rely on the shared build-metadata script (including ensuring Node is available before reading metadata).Reviewed by Cursor Bugbot for commit fa89d6b. Bugbot is set up for automated code reviews on this repo. Configure here.