@radhya/mach 2.6.6 → 2.6.8

package/README.md

@@ -343,7 +343,7 @@ mach deeplink setup \
   --output public
 ```
 
-`setup` writes compact `deepLinks` settings into `mach.config.json`, generates Apple AASA and Android `assetlinks.json` files, wires an Expo config plugin for Expo projects, and safely patches Flutter's Android manifest plus iOS entitlements/URL scheme. `mach web deploy` includes those generated association files in every web release, even when setup wrote them to a separate `public` or `deep-links` directory. When the project is linked and has a Mach-managed Android keystore, setup reads its public SHA-256 signing fingerprint automatically; the temporary keystore file is removed immediately. It then offers an optional Google Play App Signing SHA-256 field, defaulting to No. The field accepts comma-separated fingerprints and `assetlinks.json` supports more than one, so debug, direct-distribution, and Google Play builds can coexist. Developers can also add the Google Play value later with a repeatable `--android-fingerprint` flag or `deepLinks.android.sha256CertFingerprints`; it must remain the Play certificate rather than the upload-key certificate. Re-running setup is idempotent. The interactive flow can also enable iOS Web Credentials for HTTPS OAuth callbacks and Android Login Credentials for website password and passkey sharing; both remain disabled by default. For Expo apps, Mach prefers `@radhya/mach/expo-plugin`; interactive setup offers to install `@radhya/mach` locally, and `--yes` or `--install-plugin` installs it automatically. Use `--no-install-plugin` to skip package installation; if the package is missing, Mach generates a local `./plugins/withMachDeepLinks` fallback. See [Deep Links](docs/deep-links.md).
+`setup` writes compact `deepLinks` settings into `mach.config.json`, generates Apple AASA and Android `assetlinks.json` files, wires an Expo config plugin for Expo projects, and safely patches Flutter's Android manifest plus iOS entitlements/URL scheme. `mach web deploy` includes those generated association files in every web release, even when setup wrote them to a separate `public` or `deep-links` directory. When the project is linked and has a Mach-managed Android keystore, setup reads its public SHA-256 signing fingerprint automatically; the temporary keystore file is removed immediately. It then offers an optional Google Play App Signing SHA-256 field, defaulting to No. The field accepts comma-separated fingerprints and `assetlinks.json` supports more than one, so debug, direct-distribution, and Google Play builds can coexist. Developers can also add the Google Play value later with a repeatable `--android-fingerprint` flag or `deepLinks.android.sha256CertFingerprints`; it must remain the Play certificate rather than the upload-key certificate. Re-running setup is idempotent. The interactive flow can also enable iOS Web Credentials for HTTPS OAuth callbacks and Android Login Credentials for website password and passkey sharing; both remain disabled by default. For Expo apps, Mach prefers `@radhya/mach/expo-plugin`; interactive setup offers to install `@radhya/mach` locally, and `--yes` or `--install-plugin` installs it automatically. Use `--no-install-plugin` to skip package installation; if the package is missing, Mach generates a local `./plugins/withMachDeepLinks` fallback. In a multi-app Expo workspace, use one environment-aware wrapper that passes its selected `machConfigPath` to the plugin; Mach will never insert fixed product configuration into the shared root. See [Deep Links](docs/deep-links.md).
 
 ## Local Device Agent