Repository navigation
Preserve Swift and Go compatibility when upgrading PURL - #642
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
simonchrz
added a commit
to simonchrz/proxy
that referenced
this pull request
Oct 30, 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
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.
Upgrade
git-pkgs/purlto v0.2.1 andgit-pkgs/registriesto v0.13.0 while preserving existing Go retention, denylist and exact cooldown rule matching. Go module names in these policies remain case-insensitive, including cooldown exemptions.Reuse Go archives stored under lowercased PURL keys when the recorded upstream path identifies the exact requested module. Move the artifact record to the case-preserving key on cache access, retaining its stored bytes and access history. Records with an unknown or different module origin are fetched again.
Keep Swift registry cache keys under
pkg:generic/swift-registry/{scope}.{name}. Use enrichment v0.7.5 to reject unsupported Swift registry vulnerability lookups: vulnerability and version-enrichment APIs return HTTP 400 withBAD_REQUEST.Related to #613. Source-coordinate Swift policy support remains separate.