Skip to content

fix(build-mcpb): allow mixed-case owner names in name regex#53

Merged
JoeCardoso13 merged 1 commit intomainfrom
fix/conventions-mixed-case-owner-regex
Mar 17, 2026
Merged

fix(build-mcpb): allow mixed-case owner names in name regex#53
JoeCardoso13 merged 1 commit intomainfrom
fix/conventions-mixed-case-owner-regex

Conversation

@JoeCardoso13
Copy link
Copy Markdown
Contributor

Summary

  • Updated the manifest name regex in CONVENTIONS.md and phase-4-validate-bundle.md to accept mixed-case owner segments (e.g., @JoeCardoso13/stripe)
  • Added documentation that the registry normalizes the owner to lowercase

Test plan

  • Run ./scripts/validate.sh — both skills pass
  • Verify regex in both files matches: /^@[a-zA-Z0-9][a-zA-Z0-9-]{0,38}\/[a-z0-9][a-z0-9-]{0,213}$/

Closes #37

The registry normalizes owner names to lowercase (mpak#41), so the
validation regex should accept mixed-case owners like @JoeCardoso13.
Updated in both CONVENTIONS.md and phase-4-validate-bundle.md.
@mgoldsborough mgoldsborough added the qa-reviewed QA review completed with no critical issues label Mar 17, 2026
@JoeCardoso13 JoeCardoso13 merged commit 0a06b2a into main Mar 17, 2026
1 of 2 checks passed
@JoeCardoso13 JoeCardoso13 deleted the fix/conventions-mixed-case-owner-regex branch March 17, 2026 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

qa-reviewed QA review completed with no critical issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CONVENTIONS.md name regex rejects valid mixed-case owners

2 participants