chore: bump version to 0.2.2

[jjl9807]

No description provided.

[github-actions]

Claude finished @jjl9807's task in 1m 47s —— View job

---

Code Review Complete ✅

Review Summary

This PR bumps the version from 0.2.1 to 0.2.2. I've analyzed the changes and recent commit history to provide a comprehensive review.

---

🔍 Findings

✅ Positive Aspects

1. Version Consistency: Both Cargo.toml and Cargo.lock are updated consistently
2. Semantic Versioning: The patch bump (0.2.1 → 0.2.2) is appropriate for the single bug fix included
3. Clean Changes: The diff is minimal and focused only on version numbers

⚠️ Issues Identified

1. Missing CHANGELOG (Severity: Medium)

The repository lacks a CHANGELOG.md file to document version history and changes. This makes it difficult for users to understand what changed between versions.

Recommendation: Create a CHANGELOG.md following Keep a Changelog format:

# Changelog

## [0.2.2] - 2026-01-31
### Fixed
- Use qemu:///system URI to enable bridge creation (#10)

## [0.2.1] - 2026-01-29
### Added
- Fallback to TCG when KVM is unavailable (#9)
- Adjust SSH timeout based on KVM availability

Fix this →

2. Empty PR Description (Severity: Low)

The PR has no description explaining what changed or why this version bump is needed.

Recommendation: Add a description like:

Bump version to 0.2.2 to release the fix for bridge creation permissions (#10).

## Changes since 0.2.1
- fix: use qemu:///system URI to enable bridge creation (#10)

3. Unusual Branch Configuration (Severity: Low)

The PR shows main -> main which is atypical. Version bump PRs typically come from a dedicated branch (e.g., chore/bump-0.2.2).

Best Practice: For future releases:

1. Create a dedicated branch for version bumps
2. Make the changes on that branch
3. Open a PR from that branch to main
4. This allows for review before the version is tagged

4. No Git Tag (Severity: Medium)

After merging, the version should be tagged in git to mark the release point.

Post-Merge Action: After merging this PR, create and push a git tag:

git tag v0.2.2
git push origin v0.2.2

5. Changes Since Last Version

Between v0.2.1 and this PR, there is only one commit:

• 8a01d5b - fix: use qemu:///system URI to enable bridge creation (fix: use qemu:///system URI to enable bridge creation #10)

This fix addresses a permissions issue where the default qemu:///session connection couldn't create network bridges. The change to qemu:///system enables proper bridge creation for the qlbr0 network.

Assessment: A patch version bump is appropriate for this bug fix.

---

📋 Code Quality Assessment

Given the nature of this PR (version bump only), most comprehensive review criteria don't directly apply, but here's the assessment:

• Code Quality: N/A (no functional code changes)
• Security: ✅ No security concerns with version metadata changes
• Performance: ✅ No performance impact
• Testing: ⚠️ The underlying fix (commit 8a01d5b) should have tests, but version bumps don't need separate tests
• Documentation: ⚠️ Missing CHANGELOG documentation

---

✅ Recommendations Summary

Before Merge:

1. Add a PR description explaining the version bump
2. Consider creating a CHANGELOG.md file

After Merge:

1. Create and push git tag v0.2.2
2. Consider publishing to crates.io if this is a public crate

For Future Releases:

1. Use dedicated branches for version bumps
2. Maintain a CHANGELOG.md
3. Automate version bumps and tagging with CI/CD

---

✅ Approval Status

The version bump itself is technically correct and follows semantic versioning. The changes are minimal and appropriate for a patch release containing a single bug fix.

Status: ✅ Approved with recommendations for improvement

---

Tasks Completed

• Read repository guidelines (CLAUDE.md)
• Review changed files (Cargo.toml and Cargo.lock)
• Check git history for changes since last version
• Verify semantic versioning appropriateness
• Check for CHANGELOG or release notes
• Provide comprehensive review feedback

---