make cpan namespace optional - #103
Merged
petergardfjall merged 1 commit intoAug 21, 2026
Merged
Conversation
petergardfjall
force-pushed
the
cpan-optional-namespace
branch
from
August 20, 2026 11:03
f2bae8f to
3ad9fa9
Compare
Collaborator
|
The |
petergardfjall
force-pushed
the
cpan-optional-namespace
branch
from
August 21, 2026 06:54
3ad9fa9 to
569ee0d
Compare
petergardfjall
approved these changes
Aug 21, 2026
Collaborator
|
Updated the |
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
2 participants
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 purl-spec mentions on the cpan namespace that it is optional and when present it should be uppercased.
https://github.com/package-url/purl-spec/blob/ef12cbcd96cfdee33ad86f8b7fad74cf507c36c9/types/cpan-definition.json#L11