Release v2.6.0

[plfavreau]

🚀 What's new?

Release v2.6.0

🤔 Type of Change

What kind of change is this? Mark with an x

• Bug fix (non-breaking change that solves an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (update to the docs)

✅ Checklist

Before you submit, please make sure you've done the following. If you have any questions, we're here to help!

• I have read the Contributing Guide.
• My code follows the project's style guidelines (ruff check . and ruff format . pass).
• I have added necessary documentation (if applicable).

💬 Any questions or comments?

Have a question or need some help? Join us on Discord!

Summary by CodeRabbit

• Chores
  • Version bumped to 2.6.0

[coderabbitai]

Walkthrough

Version bump from 2.5.3 to 2.6.0 in pyproject.toml. No configuration, dependency, or behavioral changes made.

Changes

Cohort / File(s)	Summary
Version Update pyproject.toml	Updated project version from 2.5.3 to 2.6.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• minitap-ai/mobile-use#79: Also performs a version field bump in pyproject.toml (2.4.0→2.5.0), indicating a pattern of release versioning PRs.

Suggested reviewers

• KYN4

Poem

🐰 Hop, hop! The version grows,
From 2.5 to 2.6 it goes,
A bump so clean, a change so neat,
Our project's update is complete! 🎉

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Release v2.6.0" is fully related to the main change in the changeset, which is a version bump from 2.5.3 to 2.6.0 in pyproject.toml. The title is concise, clear, and specific—it directly describes the primary action being taken without noise or vague terminology. A teammate reviewing the repository history would immediately understand that this PR is for releasing version 2.6.0, which aligns perfectly with the PR's stated objective to release v2.6.0 as a new feature release.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-2.6.0

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ad98ebd and e3aec1c.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.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). (1)

• GitHub Check: dockerhub

🔇 Additional comments (2)

pyproject.toml (2)

3-3: Version bump is semantically correct.

The version change from 2.5.3 to 2.6.0 appropriately reflects a non-breaking feature release per semantic versioning.

---

1-161: Verify that the release process is complete.

The PR description notes that several checklist items are unchecked:

• Read Contributing Guide
• Code style/formatting checks
• Documentation additions

For a release PR, please confirm that:

1. All release checklist items have been intentionally addressed or the unchecked items are not applicable for this release.
2. All typical release artifacts (CHANGELOG, release notes, git tags, etc.) are included in this PR or are handled separately in your release workflow.
3. Code formatting and documentation have been reviewed and are in order.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}