Trust Agent Zero plugin 3.2 without breaking 3.1 - #57
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (8)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe release version changed from 0.15.2 to 0.15.3 across package metadata, dependencies, documentation, and release links. Agent Zero validation now supports matching 3.1.0/0.14 and 3.2.0/0.15 contracts. ChangesRelease and Agent Zero compatibility
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The change adds compatibility for Agent Zero plugin 3.2.0 while retaining the approved 3.1.0 contract; no actionable merge-blocking risk remains after normal checks and review. Sequence Diagram(s)sequenceDiagram
participant CapabilityDescriptor
participant CapabilityValidation
participant SupportedContracts
participant PluginYaml
CapabilityDescriptor->>CapabilityValidation: provide declared plugin and Tree Ring versions
CapabilityValidation->>SupportedContracts: match plugin and Tree Ring contract
CapabilityValidation->>PluginYaml: validate against declared plugin version
PluginYaml-->>CapabilityValidation: return version match result
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 37.50% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 8 functions across 2 files. (6 skipped: 6 unsupported.)
✨ Finishing Touches 💡 2📝 Generate docstrings 💡
🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Warning Some tools did not complete. Review the errors below. 🔧 Clippy (1.97.1)Clippy execution failed 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. Comment |
Summary
Why
The Agent Zero plugin 3.2 package needs the current Tree Ring protocol, but CLI 0.15.2 still hard-pinned plugin 3.1.0. Publishing 3.2.0 first would make real preflight fail. This patch releases the CLI-side trust contract first while keeping installed 3.1.0 packages working.
Validation
cargo fmt --all -- --checkpython3 scripts/validate-plugin-packages.pycargo test --workspace --lockedgit diff --checkAll passed locally.
High-level PR Summary
This PR bumps the Tree Ring CLI from version
0.15.2to0.15.3and implements dual-version capability trust for the Agent Zero plugin. The changes allow the CLI to accept both the legacy plugin version3.1.0(with CLI0.14.0/ minor0.14) and the new plugin version3.2.0(with CLI0.15.3/ minor0.15) through a tuple-based validation approach. This ensures backward compatibility while enabling adoption of the newer plugin version without breaking existing3.1.0installations. The trust logic now validates against a list of approved capability contracts and rejects mixed or partially upgraded tuples, preventing version conflicts during the transition period.⏱️ Estimated Review Time: 15-30 minutes
💡 Review Order Suggestion
Cargo.tomlcrates/tree-ring-memory-cli/Cargo.tomlcrates/tree-ring-memory-sqlite/Cargo.tomlCargo.lockcrates/tree-ring-memory-cli/src/activation/adapters.rscrates/tree-ring-memory-cli/tests/harness_activation_acceptance.rsREADME.mddocs/press-kit.mdmarketing/README.mdSummary by CodeRabbit
New Features
Bug Fixes
Documentation