Repository navigation
feat(switch): fetch Yarn Classic 1.x from configured npm registry - #346
Merged
Merged
Conversation
馃懛 Deploy request for yarn-v6 pending review.Visit the deploys page to approve it
|
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.
Follow-up to #292. Yarn Classic releases were still always downloaded from https://repo.yarnpkg.com/releases//. That breaks in corporate networks where repo.yarnpkg.com is blocked but npm traffic goes through a mirror such as Artifactory.
Manually checked yarn@1.22.22 end to end through an Artifactory npm mirror.