fix(sequentialthinking): read server version from package.json - #4576
Open
KarlLeen wants to merge 2 commits into
Open
fix(sequentialthinking): read server version from package.json#4576KarlLeen wants to merge 2 commits into
KarlLeen wants to merge 2 commits into
Conversation
Replace the hardcoded 0.2.0 so initialize serverInfo tracks the package version (0.6.2 in-tree; CalVer after release), matching the approach used for memory server version sync. Skip the dist-layout assertion when dist/ is absent so CI's test-before-build job (and local runs without prepare) still pass.
Spawn the built server over stdio and assert getServerVersion() matches package.json (and is not the old hardcoded 0.2.0). Skip when dist/ is absent so test-before-build CI still passes.
4 tasks
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.
Fixes #4575
Read
serverInfo.versionfrompackage.jsonat runtime instead of hardcoding"0.2.0".Published
@modelcontextprotocol/server-sequential-thinking@2026.7.4still shipsdist/index.jswithversion: "0.2.0"while itspackage.jsonis"2026.7.4". Same class of bug as #4406 for memory; related to #360.Changes
version.tswithresolvePackageVersion()(source +dist/layouts)McpServertoSERVER_VERSION"0.2.0", optional dist resolve, stdioinitializesmoke via SDK clientHow Has This Been Tested?
cd src/sequentialthinking && npm run build && npm test→ 17 passedrm -rf dist && npm test→ 15 passed, 2 skippedClient+StdioClientTransportagainstdist/index.js;getServerVersion().versionmatchespackage.jsonNote
Aligns
serverInfowithpackage.json(in-tree0.6.2). CalVer on the next publish follows whatever release writes intopackage.json(see #3870).Server Details
Breaking Changes
None.
Types of changes
Checklist