Skip to content

fix: derive MCP server version from package metadata - #13

Open
mawxcodehub wants to merge 1 commit into
GeLi2001:mainfrom
mawxcodehub:codex/use-package-version-for-mcp
Open

fix: derive MCP server version from package metadata#13
mawxcodehub wants to merge 1 commit into
GeLi2001:mainfrom
mawxcodehub:codex/use-package-version-for-mcp

Conversation

@mawxcodehub

Copy link
Copy Markdown

Summary

  • Read the MCP server version from package metadata instead of a hardcoded 1.0.0 literal.
  • Keeps the server initialization version aligned with the package version on future releases.

Closes #12

Validation

  • npm run build
  • npm pack --dry-run --json
  • node -e "const fs=require('fs'); const pkg=require('./package.json'); const js=fs.readFileSync('./dist/index.js','utf8'); if(!js.includes('package_json_1.default.version')) process.exit(1); console.log(JSON.stringify({packageVersion:pkg.version, usesPackageVersion: true}))"
  • git diff --check

Signed-off-by: MAWXHUB <130845891+mawxcodehub@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MCP server reports stale version 1.0.0 in npm package 1.0.9

1 participant