Repository navigation
v1.1.3
Fixes
-
Mobile session creation no longer times out on real devices. Bundles
@testingbot/automation-mcp0.1.7, which stops proxiedappium-mcpcalls inheriting the MCP SDK's 60 s default request timeout — far below real-device provisioning (~200 s for a free iPhone; the hub gives up at ~315 s). Previouslyappium_session_management action=createreturnedRequest timed outwhile the hub kept starting the session, so the session could be neither used nor deleted and billed until the hub reaped it.Creates now get 600 s and other proxied calls 120 s, tunable via
TESTINGBOT_APPIUM_SESSION_TIMEOUT_MSandTESTINGBOT_APPIUM_TIMEOUT_MS. See testingbot/automation-mcp#1.
Security
-
All open Dependabot alerts cleared (#1) —
npm auditreports 0 vulnerabilities:qs^6.16.0,morgan^1.12.1,@puppeteer/browsers^3.2.2, and vitest 4.1.11 for the dev-only@vitest/mockerpath traversal.This reverses the v1.1.2 decision to stay on
@puppeteer/browsers2.x: v3 drops the unpatchedextract-zipsymlink path traversal (both high alerts) but declaresengines: node >=22.12.0. That field is advisory —webdriver,@wdio/utils, and@puppeteer/browsersv3 were all verified importing cleanly on Node 20.20.2, and the browser-download paths that engine bound protects are never invoked against a remote hub. Note that the.mcpbbundle carries v3, since npm overrides apply when the bundle's runtime tree is installed; consumers installing from npm resolve v2 as before, because overrides don't propagate to dependents.
Full changelog: v1.1.2...v1.1.3