Document maestro 2.0.0 upgrade requirements

[takahirom]

What

Add documentation comment about maestro 2.0.0 availability and upgrade requirements.

Why

• Maestro 2.0.0 is available but contains significant API breaking changes
• Documents the upgrade blocker to prevent future confusion
• Provides context for future maintainers about version constraints

Technical details:

• Maestro 2.0.0 requires API compatibility fixes in Orchestra, executeCommands, iOS drivers, and element finding methods
• Current version (1.40.0) remains stable and working
• Future upgrade work can reference this documentation

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds an inline comment to the maestro version entry in gradle/libs.versions.toml. The version remains 1.40.0. No other files or declarations changed.

Changes

Cohort / File(s)	Summary
Build metadata gradle/libs.versions.toml	Appended inline comment to versions.maestro line; version stays at 1.40.0; comment notes 2.0.0 exists but requires API compatibility fixes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7d3e0a2 and 935a150.

📒 Files selected for processing (1)

• gradle/libs.versions.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)

• GitHub Check: cli-e2e-android (2, 2)
• GitHub Check: build
• GitHub Check: cli-e2e-android (1, 2)
• GitHub Check: cli-e2e-ios
• GitHub Check: cli-e2e-web
• GitHub Check: build (windows-latest)
• GitHub Check: compare-screenshot-test
• GitHub Check: store-screenshot-test
• GitHub Check: test
• GitHub Check: build (ubuntu-latest)
• GitHub Check: build (macos-latest)
• GitHub Check: build (macos-13)

🔇 Additional comments (1)

gradle/libs.versions.toml (1)

19-19: Supported version constraint keys in Gradle version catalogs TOML
In your libs.versions.toml [versions] entries Gradle (v7+ through v9.x) supports the following members for “rich” versions:

• require – minimum required version (a simple string like "1.40.0" is equivalent to require = "1.40.0").
• strictly – exact version or range that must be honored.
• prefer – a soft preference if no stronger constraint applies.
• reject – a list of version patterns to exclude.
• rejectAll – boolean flag to reject all versions.
  (docs.gradle.org)

Example syntax in [versions]:

[versions]
# simple (require = "1.40.0")
maestro             = "1.40.0"

# strictly pin to 1.40.0
maestroStrict       = { strictly = "1.40.0" }

# require 1.40.0 but reject any 2.x
maestroRequireReject = { require  = "1.40.0", reject = ["2.+"] }

# reject all versions (for testing or temporary lockdown)
maestroNoVersions   = { rejectAll = true }

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch tm/upgrade-maestro-to-2.0.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.