-
Notifications
You must be signed in to change notification settings - Fork 542
Support for "@" sign in component names #1872
Copy link
Copy link
Closed
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Metadata
Metadata
Assignees
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Is your feature request related to a problem? Please describe.
packages names in node often can have "@" sigh at the beginning. I just spent 8h trying to figure out why releases are not created for me. I was just receiving
Bad pull request title: 'chore(main): release @xyz/xyz 1.0.0'after merge. after digging in release-please code i figured out that "@" sign is creating me trouble.Describe the solution you'd like
chore(main): release @xyz/xyz 1.0.0should be a valid PR nameDescribe alternatives you've considered
Components with illegal characters in names should be at least logged on some early stage of process.
Additional context
none