@radhya/mach 2.7.1 → 2.7.3

package/README.md

@@ -218,6 +218,12 @@ in its browser cache. On short-lived Linux CI runners, cache
 worker. Use `--no-setup` only in a pre-provisioned CI image to prevent any
 dependency or browser installation.
 
+An active Playwright run can be cancelled from its **Test Runs** detail page.
+Mach records a cancellation request only; it never reaches into a developer
+machine or CI worker. The running `mach web test` command checks for that
+request every two seconds, stops its own Playwright process tree, and records
+the final result as `cancelled`.
+
 ### Keep CI web tests fast
 
 - Commit `package.json` and the matching npm, pnpm, or Yarn lockfile after the
@@ -259,6 +265,11 @@ Mach manages the test execution infrastructure for you, so projects do not need
 Managed Android Maestro runs need an APK artifact and a `.maestro` flow file or directory. By default, `mach maestro --maestro-flows .maestro` uploads the local flow folder for that run when the path exists in the current project. If the local path is not present, Mach falls back to the build source snapshot.
 Managed Android runners use emulators, so the tested APK must include `x86_64`. Mach automatically includes emulator ABI support when you build with `--maestro`, when the profile name looks like `maestro`/`e2e`/`test`, or when the build profile sets `"android": { "emulator": true }`.
 Managed Maestro is billed from the Pay as you go wallet after the runner completes. Default pricing is $0.50 for the first 15 minutes, then $0.10 per additional 10-minute block; admins can change these rates from Dashboard Admin > Pricing.
+Open an active Maestro run in **Test Runs** to cancel it. Mach terminates its
+managed Android runner immediately. Managed iOS tests are cancelled through
+their GitLab pipeline when Mach has a GitLab API control token; if that control
+is unavailable, Mach leaves the test active and explains that it could not
+verify a stop instead of reporting a false cancellation.
 Use `mach maestro --local` to run the same flows on your connected local emulator/device. With `--build-id`, Mach downloads and installs the build artifact first; without a build or artifact flag, it runs against the app already installed locally.
 Use `--maestro-env <name>` for local or managed runs that need test credentials or other dynamic values. The flag is repeatable and also accepts comma-separated names. Local runs forward only names that exist in the shell or loaded dotenv environment, and the startup log lists every forwarded name. Managed runs store requested values encrypted, pass them to the iOS or Android Maestro command, redact values from runner logs, and fall back to the Mach server environment when a value is not present in the CLI environment.