From 6b770c38dabbc808f03324b5e4382ca0f026cb7b Mon Sep 17 00:00:00 2001 From: finalerock44 Date: Tue, 4 Aug 2026 16:06:24 +0100 Subject: [PATCH] docs: add Maestro 2.7.0 and 2.8.0 Also notes what 'latest' now resolves to, and flags 2.7.0's artifact bundle change for anyone consuming test artifacts programmatically. Hold this merge until production supports both versions - main publishes. --- configuration/maestro-versions.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/configuration/maestro-versions.md b/configuration/maestro-versions.md index a309dbf..e58c97a 100644 --- a/configuration/maestro-versions.md +++ b/configuration/maestro-versions.md @@ -18,12 +18,16 @@ We currently support the following versions of Maestro: * 2.5.1 * 2.6.0 * 2.6.1 +* 2.7.0 +* 2.8.0 ## Version Selection You can specify a version using `--maestro-version `. -We additionally support the use of `--maestro-version latest` which will default to the most up-to-date version we support. +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.8.0. + +Note that Maestro 2.7.0 reorganised the per-flow debug output into a new bundle layout, with screenshots named `step--.png`. If you download and process test artifacts programmatically, check your tooling against a 2.7.0 or later run before switching. ### Examples