fix(yarn): do not set registryUrls from yarnrc on non-npm dependencies #25146
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.
Changes
Set registryUrls only if datasource is npm. Some npm dependencies are using github-tags as datasource. The lookups of the github-tags are not requested from github but from the first registryUrl (eg private artifactory registry).
Context
This but was introduced with #24455. The non-npm dependencies were returned before the registryUrls was set
https://github.com/renovatebot/renovate/pull/24455/files#diff-43bee6aaab05445cea15363ac769893671dc75dcc55db59b50801e1a6c97e8f5L257
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: