chore(registry): bump vaara-server manifest to 0.45.1#176
Conversation
The publish-npm job runs `npm publish --provenance` but never passed NODE_AUTH_TOKEN, so with NPM_PUBLISH_ENABLED on it would 401. Wire the NPM_TOKEN secret into the publish step env so tagged releases auto-publish the TypeScript client instead of relying on a manual local `npm publish` (which packs whatever stale dist/ is on disk). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
server.json (vaara proxy) was already 0.45.1; the standalone vaara-server manifest lagged at 0.45.0. Both now match the published PyPI release so the MCP registry can be bumped off 0.44.0.
|
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)
📝 WalkthroughWalkthroughVersion 0.45.1 release configuration: npm publish workflow now includes NODE_AUTH_TOKEN environment variable for authenticated publishing, and server version is bumped to 0.45.1 in the manifest. ChangesRelease 0.45.1
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Standalone vaara-server manifest lagged at 0.45.0 while server.json was already 0.45.1. Syncs main with the published registry.
Summary by CodeRabbit