@radhya/mach 2.1.1 → 2.1.3

package/README.md

@@ -435,9 +435,9 @@ Create a `mach.config.json` in your project root:
 | `ios.bundleIdentifier` | iOS bundle ID used for signing, version counter scoping, and submit                                                            |
 | `ios.appleTeamId`      | Optional global Apple Developer Team ID used for iOS signing. Profile-specific `submit.<profile>.ios.appleTeamId` overrides it |
 | `ios.ascAppId`         | App Store Connect app id used for iOS submission                                                                                |
-| `ios.buildNumber`      | Set to `"auto"` to let Mach assign the next iOS CFBundleVersion from its Dashboard counter                                     |
+| `ios.buildNumber`      | Use `"auto"` for the next Dashboard counter value, or set an explicit CFBundleVersion such as `"68"` or `"1.2.3"`              |
 | `android.package`      | Android package name used for signing, version counter scoping, and submit                                                     |
-| `android.versionCode`  | Set to `"auto"` to let Mach assign the next Android versionCode from its Dashboard counter                                     |
+| `android.versionCode`  | Use `"auto"` for the next Dashboard counter value, or set an explicit positive integer                                          |
 
 ### Profile Properties
 
@@ -536,6 +536,8 @@ When `android.versionCode` is set to `"auto"`, Mach assigns an Android versionCo
 
 When `ios.buildNumber` is set to `"auto"`, Mach assigns the next iOS CFBundleVersion from the scoped Dashboard counter. Concurrent builds are safe because the Dashboard API increments the counter atomically.
 
+When either field contains an explicit value, Mach uses that exact value without incrementing the counter. Profile-level `build.<profile>.ios.buildNumber` and `build.<profile>.android.versionCode` values override the root platform values. The resolved Mach value is authoritative: runners reuse the saved assignment, native projects receive it after Expo prebuild, and Mach rejects an artifact whose packaged value differs.
+
 This only changes iOS `CFBundleVersion` / build number. It does not bump the public App Store version (`CFBundleShortVersionString`, usually `expo.version` in `app.json`). After a version like `1.17.0` is approved/released, Apple closes that train for new uploads; bump the app version, for example to `1.17.1`, rebuild, then submit.
 
 Regular iOS development builds should set `distribution: "development"` and resolve Apple Development certificates/profiles. For custom profile names, Mach follows the profile fields, not the profile name: `environment` chooses Dashboard secrets, and `distribution` / `iosExportMethod` chooses signing. Dev-client builds can keep `distribution: "internal"` and set `developmentClient: true`; Mach will still use development signing credentials while producing an internal installable artifact.