@validate.qa/runner 1.0.34 → 1.0.36

package/README.md

@@ -39,6 +39,28 @@ Starts the runner daemon, polling for pending test runs from the cloud and execu
 npx @validate.qa/runner start
 ```
 
+### Auto-update (required)
+
+Every published runner version can change the client↔server workflow. On
+`login` / `start` / `status`, and again every ~15 minutes while running, the
+CLI checks the npm `latest` dist-tag for `@validate.qa/runner`. If your
+install is behind, the process **exits** with install instructions:
+
+```bash
+npm install -g @validate.qa/runner@latest
+validate-runner start
+```
+
+The server also rejects heartbeats from outdated local runners (HTTP 426) so
+they cannot claim new work. Cloud / shared runners are not gated by this.
+
+| Env var | Effect |
+|---------|--------|
+| `VALIDATE_RUNNER_ALLOW_OUTDATED=1` | Emergency bypass (debug / air-gapped only) |
+| `VALIDATE_RUNNER_VERSION_CHECK_MS` | Recheck interval while running (min 60s, default 15m) |
+| `RUNNER_CLOUD=true` | Skips the check (shared-runner / cloud images) |
+| `MIN_LOCAL_RUNNER_VERSION` *(server)* | Optional floor version if npm is unreachable |
+
 ---
 
 ## Commands
@@ -95,7 +117,7 @@ The runner supports native mobile app testing on:
 - **iOS:** Simulators (macOS) + Real devices via USB
 - **Android:** Emulators + Real devices via USB
 
-Tests are executed using **Appium 2** with XCUITest (iOS) and UiAutomator2 (Android) drivers.
+Tests are executed using **Appium** with XCUITest (iOS) and UiAutomator2 (Android) drivers.
 
 ### How It Works
 
@@ -150,7 +172,7 @@ Tests are executed using **Appium 2** with XCUITest (iOS) and UiAutomator2 (Andr
 - **Emulator** - Create via Android Studio → Device Manager
 
 #### Node.js
-- **Version**: Node 18 or higher
+- **Version**: Node 20 or higher
 - **npm**: Latest stable version
 
 ### Setup Steps
@@ -166,7 +188,7 @@ Expected output:
 ✓  Playwright installed
 ✓  Xcode 15.x (iOS SDK)
 ✓  Android SDK (API 34)
-✓  Appium 2.x available
+✓  Appium available
 ```
 
 #### 2. Boot a Simulator/Emulator
@@ -261,7 +283,7 @@ validate.qa Local Runner
 
 #### 6. Run Mobile Tests
 
-**Note:** The "Run Test" button in the UI is currently disabled for mobile tests (shows "Run Pending"). Tests execute automatically when:
+The **Run Test** button queues Appium tests directly. A queued mobile run starts when:
 
 1. You queue a run from the dashboard
 2. The runner is online with `--mobile` flag
@@ -296,7 +318,7 @@ npx @validate.qa/runner start --mobile
 ```
 
 Enables:
-- Appium 2 server (port 4723)
+- Appium server (port 4723)
 - Mobile bridge server (port 9515)
 - Device discovery and capabilities reporting
 - iOS Simulator + Android Emulator support
@@ -305,7 +327,7 @@ Enables:
 
 | Feature | Web Tests | Mobile Tests |
 |---------|-----------|--------------|
-| Framework | Playwright | Appium 2 |
+| Framework | Playwright | Appium |
 | Browser/Device | Headless Chromium | iOS Simulator / Android Emulator |
 | Locator Strategy | CSS selectors, XPath | Accessibility ID, XPath, Resource ID |
 | Actions | click, fill, navigate | tap, type, swipe, back, home |
@@ -529,10 +551,11 @@ npm publish --access public
 
 ### Version
 
-**Current:** 1.0.0
+**Current:** 1.0.35
 
 **Changelog:** See [git history](https://github.com/Validate-QA/validate.qa/commits/main/packages/runner) for the full change log. Recent highlights:
 
+- **1.0.35** - Force-upgrade gate: outdated installs exit when a newer package is on npm (workflow changes every release)
 - **1.0.0** - First stable release
 - **0.1.10** - Rename package to `@validate.qa/runner`; API test capabilities; discovery pipeline refactor
 - **0.1.9** - Mobile execution improvements; mobile bridge security hardening