fix(purl): url-encoded slashes in purl#5592
Open
jess-lowe wants to merge 1 commit into
Open
Conversation
G-Rath
approved these changes
Jul 3, 2026
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.
fixes #5590
When the database worker was migrated from Python to Go, it began using Go's purl.Generate function to generate PURLs. In Go, ecosystems like Packagist, npm, Hex, and SwiftURL were registered to use
simpleGeneratorwhich did not separate package name into namespace and name components. As a result, the entire package name (e.g.drupal/colorbox) was passed as the package name parameter. The underlying Go package-url library correctly URL-encoded the slash, producingpkg:composer/drupal%2Fcolorbox.