Repository navigation
fix(registry): opis server.json poniżej limitu 100 znaków + retry publikacji do rejestru - #21
Merged
Merged
Conversation
The MCP registry rejected the v0.7.5 publish with a 422: the description was 105 characters against a limit of 100. It only validates at publish time, i.e. after npm has already gone out, so the registry sat a version behind while npm was current. - trim the description to 93 characters - add tests/server-manifest.test.ts so CI catches the registry's constraints (description length, server name vs package.json#mcpName, npm identifier) before a release instead of halfway through one - allow `workflow_dispatch` with publish_registry=true to re-run just the registry half against the current server.json, and verify the target version actually exists on npm before pointing the registry at it Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Summary
descriptionwserver.jsonmiało 105 znaków przy limicie 100. Zastany błąd w manifeście, nie regresja migracji. Opis skrócony do 93 znaków.tests/server-manifest.test.tssprawdza w CI ograniczenia rejestru (długość opisu, zgodnośćnamezpackage.json#mcpName, identyfikator npm) — rejestr waliduje dopiero przy publikacji, czyli już PO wypuszczeniu na npm, więc taki błąd zostawia rejestr wersję w tyle.workflow_dispatchzpublish_registry=truepowtarza samą połowę rejestrową względem bieżącegoserver.json, z weryfikacją, że dana wersja faktycznie istnieje na npm.Test plan
npm run lint,npm run test:run(256 testów) — zielonegh workflow run release.yml -f publish_registry=trueaktualizuje wpis w rejestrze na 0.7.5🤖 Generated with Claude Code