chore(runway): cherry-pick ci: split push-eas-update into two parallel jobs#30724
Merged
joaoloureirop merged 1 commit intoMay 28, 2026
Merged
Conversation
…l jobs (#30399) ## **Description** Splits the `push-eas-update` job into two parallel jobs, one per platform (iOS and Android), running on separate runners. This avoids LavaMoat serializer contention and mitigates intermittent OTA deployment failures caused by a [known GitHub Actions runner issue](actions/runner#3819 (comment)). The shared EAS update steps have been extracted into a reusable workflow. ## **Changelog** CHANGELOG entry: null ## **Related issues** Fixes: N/A ## **Manual testing steps** | Run | Platform | Result | |-----|----------|--------| | [iOS dry-run](https://github.com/MetaMask/metamask-mobile/actions/runs/26117723683/job/76811308433) | iOS | ✅ Passed — cancelled before EAS upload | | [Android test](https://github.com/MetaMask/metamask-mobile/actions/runs/26119164078) | Android | ✅ Passed | | [Both platforms in parallel](https://github.com/MetaMask/metamask-mobile/actions/runs/26120507757) | iOS + Android | ✅ Both passed | ## **Before/After** ### **Before** Single `push-update` job — iOS bundled first, then Android sequentially on the same runner. ### **After** Two parallel jobs (`push-update-ios`, `push-update-android`) running simultaneously on isolated runners, visible as side-by-side nodes in the Actions run graph. Verified via dry-run dispatch targeting `exp` channel.
Contributor
|
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. |
joaoloureirop
approved these changes
May 28, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Splits the
push-eas-updatejob into two parallel jobs, one perplatform (iOS and Android), running on separate runners. This avoids
LavaMoat serializer contention and mitigates intermittent OTA deployment
failures caused by a known GitHub Actions runner
issue.
The shared EAS update steps have been extracted into a reusable
workflow.
Changelog
CHANGELOG entry: null
Related issues
Fixes: N/A
Manual testing steps
Before/After
Before
Single
push-updatejob — iOS bundled first, then Android sequentiallyon the same runner.
After
Two parallel jobs (
push-update-ios,push-update-android) runningsimultaneously on isolated runners, visible as side-by-side nodes in the
Actions run graph. Verified via dry-run dispatch targeting
expchannel. b4dffea