Maestro Versions

Device Cloud supports multiple Maestro versions to ensure compatibility with your test flows.

By default, tests currently run using Maestro 2.2.0. From 19 October 2026 the default becomes Maestro 2.10.0. Pin --maestro-version if you need to stay on a specific version (2.2.0 itself is removed on the same date, see below).

The default Maestro version will change to 2.10.0 on the 19th October 2026.

Please note that we periodically remove support for older versions so we always recommend you stay up to date.

Available Versions

We currently support the following versions of Maestro:

• 2.0.4 (deprecated)

• 2.0.9 (deprecated)

• 2.1.0 (deprecated)

• 2.2.0 (deprecated)

• 2.5.0 (deprecated)

• 2.5.1 (deprecated)

• 2.6.0 (deprecated)

• 2.6.1

• 2.7.0

• 2.8.0

• 2.9.0

• 2.10.0

• 2.11.0

Maestro 2.0.4, 2.0.9, 2.1.0, 2.2.0, 2.5.0, 2.5.1 and 2.6.0 are deprecated and will be removed on 19 October 2026. Runs pinned to these versions will fail after that date, so move --maestro-version to 2.6.1 or newer. See the Maestro Support Policy for more information.

Version Selection

You can specify a version using --maestro-version <version>.

We additionally support the use of --maestro-version latest which will default to the most up-to-date version we support. This currently resolves to 2.11.0.

Note that Maestro 2.7.0 reorganised the per-flow debug output into a new bundle layout, with screenshots named step-<number>-<command>.png. If you download and process test artifacts programmatically, check your tooling against a 2.7.0 or later run before switching.

Examples

# Use a specific version of Maestro
dcd cloud ... --maestro-version 2.10.0

# Always use the most recent version of Maestro available
dcd cloud ... --maestro-version latest

Maestro Support Policy

We will always aim to support the latest versions of Maestro and additionally continue to provide support for previous versions. Our policy for this is as follows:

• We will always add support for new versions.

• Once a new minor version has been released (i.e. 2.x.0), we'll mark all previous patches of the previous minor (i.e. 2.6.x) bar the latest as deprecated.

• Once a minor version is five versions old, we'll mark it as deprecated.

• Deprecated versions are then removed after 30 days provided it's total usage over seven days is less than 0.5%.

For example, Maestro 2.0.0 received 10 patch releases (2.0.1 -> 2.0.10) and we provided support for all of them. Once Maestro 2.1.0 released, we would then deprecate support for 2.0.0 -> 2.0.9 and retain 2.0.10.

Once Maestro 2.5.0 is released, we would then mark 2.0.10 as deprecated and look to remove it after 30 days, provided it's usage has dropped below 0.5%.

We may update the default version from time to time and we will always provide at least 30 days of notice beforehand.

We will always provide at least 30 days of warning before removing support for previous Maestro versions.