Skip to content

fix: use actual package version for MCP server responses#23

Open
nick4eva wants to merge 2 commits intob1ff:masterfrom
nick4eva:use-proper-mcp-versions
Open

fix: use actual package version for MCP server responses#23
nick4eva wants to merge 2 commits intob1ff:masterfrom
nick4eva:use-proper-mcp-versions

Conversation

@nick4eva
Copy link
Copy Markdown
Contributor

@nick4eva nick4eva commented Mar 23, 2026

Summary

  • Replace hardcoded MCP server versions ("0.1.0" in Jira/Bitbucket, "1.0.0" in Confluence) with the actual version from each package's package.json
  • Uses createRequire + import.meta.url to read package.json at runtime, so the version stays in sync automatically with releases

Problem

All three MCP servers reported incorrect hardcoded versions in their initialize response. Jira and Bitbucket reported 0.1.0, Confluence reported 1.0.0, while the actual
published version is 0.13.0.

@nick4eva nick4eva force-pushed the use-proper-mcp-versions branch from cb761c7 to 72b5675 Compare March 23, 2026 09:35
@nick4eva nick4eva force-pushed the use-proper-mcp-versions branch from 72b5675 to d1f5e5b Compare March 23, 2026 09:37
@nick4eva nick4eva changed the title fix: use proper MCP versions in MCP output fix: use actual package version for MCP server responses Mar 23, 2026
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.

1 participant