Release 1.7.0

[mamoodi]

• I have read and reviewed the documentation changes to the best of my ability.
• If the change is significant, I have run the documentation site locally and confirmed it renders as expected.

Summary of changes

Doc changes for Release 1.7.0

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
all-hands-ai	🟢 Ready	View Preview	May 1, 2026, 1:32 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[all-hands-bot]

Taste Rating: 🟡 Acceptable - Standard release version bump

[TESTING GAPS]

• No Evidence: The PR description lacks proof that the referenced Docker images exist and work together. Before merging, verify:
  1. docker.openhands.dev/openhands/openhands:1.7 is published and pullable
  2. ghcr.io/openhands/agent-server:1.19.1-python is published and pullable
  3. These versions work correctly together (e.g., successful installation test)

If these versions don't exist yet, merging this PR will break all new installations following the documentation.

[RISK ASSESSMENT]

• Overall PR: ⚠️ Risk Assessment: 🟡 MEDIUM

Documentation-only changes with no code execution risk, but high user impact if versions are not yet published. All installation commands across 7 documentation files reference these versions. A missing or broken image will cause immediate failures for new users.

VERDICT:
✅ Worth merging - Assuming versions are published and tested
❌ Needs verification first - If versions aren't confirmed available

KEY INSIGHT:
Release documentation must be synchronized with actual published artifacts; verify Docker images exist before updating references.

---

Improve this review? If any feedback above seems incorrect or irrelevant to this repository, you can teach the reviewer to do better:

1. Add a .agents/skills/custom-codereview-guide.md file to your branch (or edit it if one already exists) with the /codereview trigger and the context the reviewer is missing. See the customization docs for the required frontmatter format.
2. Re-request a review - the reviewer reads guidelines from the PR branch, so your changes take effect immediately.
3. When your PR is merged, the guideline file goes through normal code review by repository maintainers.

Resolve with AI? Install the iterate skill in your agent and run /iterate to automatically drive this PR through CI, review, and QA until it's merge-ready.

[hieptl]

Thank you! 🙏