chore: bump MCP registry manifests to 0.51.0#187
Conversation
The v0.51.0 commit bumped pyproject, __init__, CHANGELOG and the TS client but missed both MCP manifests, which still read 0.50.0. The Release workflow publishes server.json and server-vaara-server.json to the MCP Registry and then asserts the registry's latest active version equals the tag, so a v0.51.0 tag would fail that gate exactly as v0.49.0 did. Bump both the listing version and the pypi package version in each manifest. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 51 minutes and 5 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 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 |
Follow-up to #186 (v0.51.0). The v0.51.0 commit bumped pyproject,
__init__, CHANGELOG and the TS client but missed both MCP manifests (server.json,server-vaara-server.json), which still read 0.50.0.The Release workflow publishes both manifests to the MCP Registry and then asserts the registry's latest active version equals the tag. With manifests at 0.50.0 a v0.51.0 tag fails that gate, exactly as the v0.49.0 release did. This bumps the listing version and the pypi package version in both manifests so the v0.51.0 tag publishes cleanly.
🤖 Generated with Claude Code