chore(meta): record the #208 description fix under Unreleased and pin both listing caps with a test - #210
Open
m1ngshum wants to merge 1 commit into
Open
chore(meta): record the #208 description fix under Unreleased and pin both listing caps with a test#210m1ngshum wants to merge 1 commit into
m1ngshum wants to merge 1 commit into
Conversation
… both listing caps with a test #208 fit package.json's description into npm's 255-char registry cap and docs/registry-entry.json's into the MCP Registry schema's maxLength 100, but merged without a CHANGELOG entry, so the next release's notes would not say the truncated listing #207 delivered in v0.39.1 was fixed. Adds that entry under [Unreleased] so it rides the next release rather than justifying one. Neither cap is enforced by npm pack, tsc or CI — a future SEO edit would repeat #208 unseen until the next publish — so a two-assertion test now pins them. Each assertion mutation-verified: lowering its cap fails that test alone, and the failure message reports the measured length (232 and 100).
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
1 participant
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.
Summary
Follow-up to #208, which fit
package.json'sdescriptioninto npm's 255-character registry cap (the v0.39.1 listing rendered "... VS Code, Win") anddocs/registry-entry.json's into the MCP Registry schema'smaxLength: 100, but merged with no CHANGELOG entry.### Fixedentry under[Unreleased]so the fix rides the next release's notes instead of justifying a release of its own.src/__tests__/package-metadata-caps.test.ts: two assertions pinning both caps. Neither cap is enforced bynpm pack,tscor CI, so a future SEO edit would repeat chore(meta): fit the npm description in the 255-char cap and the registry template in its 100-char cap #208 unseen until the next publish.Verification
npm view @getmcpm/cli descriptionis exactly 255 chars, tail"VS Code, Win"; published version 0.39.1.main's description measured at 232 chars; registry entry at 100; schemamaxLength: 100confirmed in the 2025-12-11server.schema.json.expected 232 to be less than or equal to 200); cap 100→90 fails only the registry test (expected 100 to be less than or equal to 90).pnpm run typecheckclean;pnpm test2933/2933 green.Takes effect on npm at the next publish.