fix(server-memory): read version from package.json instead of hardcoding#4444
Closed
amerilain wants to merge 2 commits into
Closed
fix(server-memory): read version from package.json instead of hardcoding#4444amerilain wants to merge 2 commits into
amerilain wants to merge 2 commits into
Conversation
The server-info version in the memory server was hardcoded as '0.6.3', which doesn't match the actual npm package version (2026.1.26). This change reads the version dynamically from package.json at runtime, so it always reflects the published package version. Fixes modelcontextprotocol#4406
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes #4406.
The
serverInfo.versionin the memory server was hardcoded as"0.6.3", which has not matched the actual npm package version since the transition to calendar versioning (2025.4.25onward).Change
This PR reads the version dynamically from
package.jsonat runtime usingcreateRequire, so the reported version always reflects the published package version.Testing
createRequireimport patternImpact
No runtime behavior change beyond the version string. Fixes a confusing discrepancy where memory-server reported
"0.6.3"regardless of the installed version.