chore: claim lobehub hevy-mcp - #712
Conversation
There was a problem hiding this comment.
Code Review
This pull request adds a changeset file and a new plugin manifest, lhm.plugin.json, for the Hevy MCP Server. Feedback is provided regarding a version mismatch in the manifest file, which should be updated to match the package version.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| "identifier": "chrisdoc-hevy-mcp", | ||
| "name": "Hevy MCP Server", | ||
| "tags": ["hevy", "fitness", "workouts", "health", "mcp"], | ||
| "version": "3.3.0" |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe plugin manifest is updated with version ChangesPlugin release metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Poem
✨ 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 |
PR Summary by QodoAdd LobeHub plugin manifest for Hevy MCP server
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
PR Summary by QodoRegister/claim Hevy MCP server for LobeHub
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
MCP tool token costMeasured with
Change from baseline
Per-tool changes
Per-tool breakdown
Per-tool counts encode each complete tool object independently. The total encodes the complete |
Bundle ReportBundle size has no change ✅ |
There was a problem hiding this comment.
✨ PR Review
The PR adds a new Hevy MCP plugin registration entry and an accompanying empty changeset. The plugin JSON looks well-structured, but the changeset does not follow the project's stated convention for user-facing changes.
1 issues detected:
🧹 Maintainability - `npx changeset --empty` was used for a user-facing registry addition; a versioned changeset with a package bump is required instead.
Details: The changeset file is empty (just the YAML front-matter delimiters with no package/version bump entries). According to the project's contribution rules, an empty/no-op changeset is reserved for internal-only changes such as docs, CI, tests, and refactors. Adding a new publicly-discoverable plugin to the registry is a user-facing, runtime-visible change and should carry a proper versioned changeset.
File: .changeset/old-cobras-stop.md (1-2)
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #712 +/- ##
=======================================
Coverage 95.45% 95.45%
=======================================
Files 47 47
Lines 2090 2090
Branches 575 575
=======================================
Hits 1995 1995
Misses 32 32
Partials 63 63 ☔ View full report in Codecov by Harness. |
Code Review by Qodo
Context used✅ Compliance rules (platform):
65 rules 1. Stale plugin version
|
| "description": "Manage Hevy workouts, routines, folders, body measurements, and exercise templates from MCP clients through the Hevy API.", | ||
| "homepage": "https://github.com/chrisdoc/hevy-mcp", | ||
| "icon": "https://github.com/chrisdoc.png", | ||
| "identifier": "chrisdoc-hevy-mcp", |
There was a problem hiding this comment.
1. Stale plugin version 🐞 Bug ≡ Correctness
The newly added lhm.plugin.json hardcodes version "3.3.0" while the repo’s current package/server version is "3.4.0", creating inconsistent metadata for any tooling/registry that reads this plugin manifest. This drift is likely to cause incorrect version display/update behavior unless the version is intentionally independent and documented.
Agent Prompt
### Issue description
`lhm.plugin.json` declares `"version": "3.3.0"`, but the repository’s current version is `3.4.0` (as reflected in `package.json` and `server.json`). This creates inconsistent version metadata.
### Issue Context
This PR introduces `lhm.plugin.json` as a new manifest file; if it is consumed by external registries (e.g., LobeHub) it should reflect the current released version, or else explicitly document why it differs.
### Fix Focus Areas
- lhm.plugin.json[9-12]
- package.json[1-4]
- server.json[1-16]
### Suggested fix
- Update `lhm.plugin.json` `version` to `3.4.0` to match `package.json`/`server.json`.
- If the version is meant to be independent, add a short comment in project docs explaining the divergence and how/when it should be updated.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
✨ PR Description
Purpose: Register Hevy MCP Server plugin with LobeHub ecosystem by creating plugin manifest and changelog entry.
Main changes:
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how
Summary by CodeRabbit
Chores
Documentation