fix(mcp): pin matching core package version - #1231
Conversation
|
@cmondragon023 is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
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 selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe MCP package now pins ChangesMCP version alignment
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This localized change keeps the MCP and core package versions synchronized and adds coverage to prevent future mismatches; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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
@agentmemory/mcp@0.9.29to the exact matching@agentmemory/agentmemory@0.9.29core packageCloses #668
Testing
node_modules/.bin/vitest run test/consistency.test.ts— 9 tests passednode_modules/.bin/vitest run --exclude test/integration.test.ts— 151 test files passed, 1 skipped; 1,657 tests passed, 1 skippedgit diff --checkSummary by CodeRabbit