@radhya/mach 1.8.5 → 1.8.12

package/README.md

@@ -143,7 +143,7 @@ definitions:
           - mach submit --latest --platform android --profile $MACH_SUBMIT_PROFILE --track ${MACH_ANDROID_TRACK:-internal} --release-status ${MACH_ANDROID_RELEASE_STATUS:-completed} ${MACH_ANDROID_ROLLOUT:+--rollout $MACH_ANDROID_ROLLOUT} ${MACH_ANDROID_CHANGES_NOT_SENT_FOR_REVIEW:+--changes-not-sent-for-review}
 ```
 
-Android submission uses the Google Play Developer API directly, so Bitbucket/Linux runners do not need Ruby or Fastlane for `.aab` uploads. iOS submission still uses Fastlane `pilot`; run it on the macOS GitLab runner, the same runner class used for iOS builds.
+Android submission uses the Google Play Developer API directly, so Bitbucket/Linux runners do not need Ruby or Fastlane for `.aab` uploads. Mach still writes Android submission status to the submissions table, which gives the Dashboard the same history view without starting the macOS runner. iOS submission is queued through Mach and executed on the configured macOS GitLab runner, so the public command is the same from macOS, Linux, Windows, or CI.
 
 Required Bitbucket variables:
 
@@ -161,16 +161,44 @@ Required Bitbucket variables:
 
 Before enabling CI, make sure `mach.config.json` is committed, credentials are uploaded in the Dashboard, and Android service credentials are attached to the exact package id.
 
-For iOS submit, use a macOS GitLab runner:
+For iOS submit, the user-facing command is universal:
+
+```bash
+mach submit --latest --platform ios --profile $MACH_SUBMIT_PROFILE
+```
+
+The macOS runner executes the internal runner command after the Mach API triggers GitLab:
 
 ```yaml
-submit_ios:
+skye_m4_ios_submit:
+  stage: submit
   tags:
-    - macos
-  script:
-    - npm ci
-    - npm install -g @radhya/mach@latest
-    - mach submit --latest --platform ios --profile $MACH_SUBMIT_PROFILE
+    - m4-mini
+    - ios-build
+  rules:
+    - if: '$MACH_ACTION == "submit_ios"'
+      when: on_success
+    - when: never
+  script: |
+    source ~/.zshrc || source ~/.bashrc || true
+    export AWS_DEFAULT_REGION="ap-south-1"
+
+    export MACH_TOKEN=$(aws ssm get-parameter \
+      --name "/skye/submissions/$SUBMIT_ID/token" \
+      --with-decryption \
+      --query 'Parameter.Value' \
+      --region ap-south-1 \
+      --output text)
+
+    aws ssm delete-parameter --name "/skye/submissions/$SUBMIT_ID/token" --region ap-south-1 || true
+
+    if [ -n "${BUILD_ID:-}" ]; then
+      mach submit --local --submit-id "$SUBMIT_ID" --project-id "$PROJECT_ID" --platform ios --profile "${MACH_SUBMIT_PROFILE:-production}" --build-id "$BUILD_ID"
+    else
+      mach submit --local --submit-id "$SUBMIT_ID" --project-id "$PROJECT_ID" --platform ios --profile "${MACH_SUBMIT_PROFILE:-production}" --latest
+    fi
+  after_script:
+    - aws ssm delete-parameter --name "/skye/submissions/$SUBMIT_ID/token" --region ap-south-1 2>/dev/null || true
 ```
 
 ## Credential Management
@@ -378,7 +406,7 @@ mach credentials:service --platform android --package-name com.example.app --fil
 
 Android submit reads `submit.<profile>.android.track`, `submit.<profile>.android.releaseStatus`, and optional `submit.<profile>.android.rollout`, falling back to `submit.production.android.*`, then `internal` / `completed`. Valid Google Play release status values are `completed`, `draft`, `halted`, and `inProgress`. Use `rollout` only with `inProgress` or `halted`; it must be greater than `0` and less than `1`.
 
-Android submit does not require Fastlane. Mach uploads the `.aab`, assigns the returned `versionCode` to the requested track, and commits the edit through the Google Play Developer API. Transient Google Play failures are retried up to four times before the command fails. iOS submit uses Fastlane `pilot`; run it from a macOS GitLab runner. If `--ssh-host` or `submit.<profile>.ios.sshHost` is set, Mach can also upload the `.ipa` and App Store Connect API key to that macOS runner, run `pilot` remotely, then remove the remote temp files.
+Android submit does not require Fastlane. Mach uploads the `.aab`, assigns the returned `versionCode` to the requested track, commits the edit through the Google Play Developer API, and records the submission in the Dashboard. Transient Google Play failures are retried up to four times before the command fails. iOS submit queues a managed submission through Mach and runs Fastlane `pilot` on the macOS GitLab runner. Runner jobs call `mach submit --local ...`; users and CI call the normal `mach submit --platform ios ...` command. If `--ssh-host` or `submit.<profile>.ios.sshHost` is set, Mach can also upload the `.ipa` and App Store Connect API key to that macOS runner, run `pilot` remotely, then remove the remote temp files.
 
 If `--profile` is provided with `--latest`, Mach chooses the latest successful build from that profile only. This avoids accidentally submitting a staging or preprod build to production.