Repository navigation
fix(registry): shorten server.json description to fit the registry's 100-char cap - #9
Merged
Merged
Conversation
…100-char cap Commit-Author: claude-main Task-Source: user-prompt Reason: the previous 1.3.2 registry publish failed 422 validation (expected length <= 100 on body.description); the operator approved a 97-char replacement covering the same four product lines plus x402. package.json's longer description is intentionally left unchanged since npm has no such limit.
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
expected length <= 100onbody.description.server.json'sdescriptioncovering the same four product lines (SMS verification, rentals, proxies, cloud browser) plus x402 deposits.package.json's longer 168-char description is intentionally left unchanged — npm has no such length limit.Scope
server.jsononly. No version bump, no npm publish, no other metadata changes.