chore: gate npm description length in release readiness check#519
Merged
Conversation
creatornader
enabled auto-merge (squash)
July 14, 2026 23:07
creatornader
disabled auto-merge
July 14, 2026 23:08
creatornader
enabled auto-merge (squash)
July 14, 2026 23:08
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.
The npm registry stores package descriptions truncated at 255 characters; @atrib/verify-mcp@1.0.0 shipped cut mid-word (corrected text lands as 1.0.1 via #517). This adds the missing pre-publish gate: check-release-publish-readiness.mjs now fails when any non-private workspace package description exceeds the limit, listing the offenders with lengths. Negative-tested against a synthetic 294-char description (fails with the expected message) and green against current main (all 20 public packages within the limit).