fix(owner): use scoped registry for user lookup#9786
Open
martinrrm wants to merge 1 commit into
Open
Conversation
Resolve owner identities through the same scoped registry used for package reads and ownership mutations. Add regression coverage for cross-registry substitution in owner add and remove. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 1e1231bc-474e-4a27-8b78-242366f48e19
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
1 participant
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.
Summary
Ensure
npm owner addandnpm owner rmresolve users from the same registry used for the target package.The user lookup now receives the package
spec, allowingnpm-registry-fetchto honor scoped registry configuration instead of falling back to the global registry.Testing
Added regression coverage for split global/scoped registry configurations, including: