[tarrencev]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Version bumped from 1.8.1 to 1.8.2 across all packages.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Ohayo sensei! 🎌

Walkthrough

This pull request bumps the version number from 1.8.1 to 1.8.2 across six package manifest files in the sozo project. No dependencies, features, or functional code changes are introduced. Only the version field in each [package] section is updated.

Changes

Cohort / File(s)	Summary
Version Bumps bin/sozo/Cargo.toml, crates/sozo/mcp/Cargo.toml, crates/sozo/ops/Cargo.toml, crates/sozo/signers/Cargo.toml, crates/sozo/ui/Cargo.toml, crates/sozo/walnut/Cargo.toml	Version field updated from 1.8.1 to 1.8.2 in all six package manifests

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

This is a purely mechanical, homogeneous change across multiple files with identical scope—no logic modifications, no dependencies altered, and no functional impact. Verification requires only confirming that the version strings match consistently across all files.

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 title clearly and accurately summarizes the main change—preparing a version bump release for sozo from 1.8.1 to 1.8.2 across all package manifests.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 54544bc and 0a40788.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (6)

• bin/sozo/Cargo.toml (1 hunks)
• crates/sozo/mcp/Cargo.toml (1 hunks)
• crates/sozo/ops/Cargo.toml (1 hunks)
• crates/sozo/signers/Cargo.toml (1 hunks)
• crates/sozo/ui/Cargo.toml (1 hunks)
• crates/sozo/walnut/Cargo.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: fmt

🔇 Additional comments (6)

crates/sozo/walnut/Cargo.toml (1)

4-4: Ohayo sensei! Version bump is clean. ✓

The walnut crate version bump from 1.8.1 to 1.8.2 is straightforward with no dependency or configuration changes.

crates/sozo/ui/Cargo.toml (1)

4-4: Ohayo sensei! Version bump looks solid. ✓

Clean version update for sozo-ui from 1.8.1 to 1.8.2 with no dependency changes.

crates/sozo/signers/Cargo.toml (1)

7-7: Ohayo sensei! Version bump approved. ✓

Sozo-signers version updated cleanly from 1.8.1 to 1.8.2, no dependency modifications.

crates/sozo/mcp/Cargo.toml (1)

4-4: Ohayo sensei! MCP version bump is ready. ✓

Version updated from 1.8.1 to 1.8.2. External dependencies (rmcp dev rev and schemars) remain pinned and stable.

bin/sozo/Cargo.toml (1)

4-4: Ohayo sensei! Main binary version bump is solid. ✓

Sozo binary version bumped from 1.8.1 to 1.8.2. All internal crate dependencies use workspace references, ensuring they'll pick up the new version consistently.

crates/sozo/ops/Cargo.toml (1)

4-4: Ohayo sensei! Ops crate version bump confirmed. ✓

Version updated from 1.8.1 to 1.8.2 with internal dependencies properly managed via workspace references. Release preparation looks complete!

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

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