Repository navigation
Use purl's ComparisonForm for package identity - #589
Merged
Merged
Conversation
The per-ecosystem rules for when two spellings name the same package (PEP 503, NuGet case, Composer's leading v, conda channel, OCI paths, Swift registry case) now live in purl. The denylist keeps only the proxy's own pkg:generic/swift-registry spelling and the gem platform match. Keys, cache paths and stored PURLs are unchanged.
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
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.
Closes #563.
The per-ecosystem rules for when two spellings name the same package now come from purl's
ComparisonForm(git-pkgs/purl#50) instead of the denylist's own switch: PEP 503 for PyPI, NuGet case, Composer's leadingv, the conda channel, OCI paths and Swift registry case.What stays in the proxy:
pkg:generic/swift-registry/{scope}.{name}spelling, which is the proxy's own. The denylist maps it topkg:swift/{scope}/{name}before comparing.The NuGet retention key uses the comparison form too. Denylist keys, cache paths and stored PURLs are unchanged; the existing denylist and retention tests pass as they are.
go.mod points at a pseudo-version of purl main until #50 is in a release. I'll switch it to the tag then.