From 7a55c35425303ea9438f6064a758c10c3ce19af8 Mon Sep 17 00:00:00 2001
From: "omegent-app[bot]" <306514130+omegent-app[bot]@users.noreply.github.com>
Date: Thu, 6 Aug 2026 06:20:51 +0000
Subject: [PATCH] fix(mobile): declare the release_branch input on EAS
 development

The first fork/dev sync merge passed every required check and still ended as a
failed run: Dispatch Mobile Releases got HTTP 422 "Unexpected inputs provided:
[release_branch]" from mobile-eas-development.yml. Because the deploy poller
only promotes a SHA whose fork-ci run concluded success, that failure blocked
server, Discord, desktop and VS Code deployment of ae4719b1c entirely.

#344 added the release_branch input declaration to mobile-eas-production.yml
but only rewrote the usages in mobile-eas-development.yml, leaving it
referencing inputs.release_branch without declaring it. The YAML validation in
that PR printed the default for production and nothing for development, which
was the evidence and was read past.

Declare the input with the same fork/integration default so a manual dispatch
that omits it is unchanged.

Checked all three workflows for inputs.* references with no matching
declaration; none remain.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
---
 .github/workflows/mobile-eas-development.yml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/.github/workflows/mobile-eas-development.yml b/.github/workflows/mobile-eas-development.yml
index 8acfae77be8..c9028599aea 100644
--- a/.github/workflows/mobile-eas-development.yml
+++ b/.github/workflows/mobile-eas-development.yml
@@ -24,6 +24,11 @@ on:
         description: "Exact release-branch SHA (blank uses that branch's current tip)"
         required: false
         type: string
+      release_branch:
+        description: "Release branch that must contain the SHA"
+        required: false
+        type: string
+        default: fork/integration
 
 concurrency:
   group: mobile-eas-development