chore(runway): cherry-pick chore(ci): enable RC rolling builds

[runway-github]

• chore(ci): enable RC rolling builds (chore(ci): enable RC rolling builds #28680)

Description

Adds rolling builds for the Auto RC builds workflow
(.github/workflows/build-rc-auto.yml) by setting a concurrency
group on github.workflow + github.ref with cancel-in-progress: true.

When a new run starts for a given release/* branch, any queued or
in-progress run of the same workflow for that branch is cancelled,
so only the latest push is built. This mirrors Bitrise-style rolling
builds and avoids piling up redundant RC builds when the release branch
gets several commits in a short time.

Changelog

CHANGELOG entry: null

internal CI behavior only.

Related issues

Fix: https://consensyssoftware.atlassian.net/browse/MCWP-518

Manual testing steps

N/A — CI-only change. Verify by pushing multiple commits quickly to a
labeled release PR and confirming older Auto RC workflow runs are
cancelled while the newest run proceeds. 0805e78

[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 only changed file is .github/workflows/build-rc-auto.yml. The change adds:

1. A comment block explaining "rolling builds" behavior
2. A concurrency block (group: ${{ github.workflow }}-${{ github.ref }}, cancel-in-progress: true) that cancels queued/in-progress runs of the same workflow on the same branch when a new run starts.

This is a pure CI/CD infrastructure change that:

• Does not touch any application source code
• Does not touch any test code or test infrastructure (no tests/*, no page-objects, no fixtures)
• Does not affect any controllers, Engine, or core modules
• Only changes how GitHub Actions handles concurrent workflow runs for the RC build pipeline

No E2E tests are needed to validate this change — it's a GitHub Actions configuration optimization that cannot be validated by Detox tests. No performance tests are needed either.

Performance Test Selection:
The change is purely a GitHub Actions workflow configuration update (adding a concurrency group). There is no application code change, no UI rendering change, no data loading change, and no impact on app performance whatsoever.

View GitHub Actions results

[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