Use nuget.org for publicly available packages #776
Conversation
This file contains 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
When package dependency versions change, the libman package feed (hosted on the azure-public ADO instance) is not writable by non-Microsoft employees. This can lead to issues building the solution when adding/updating references, especially including when runtime packages update from SDK servicing. This change fetches any publicly available packages from nuget.org, which makes it easier to support new packages or package upgrades. Having multiple package sources is not a risk when using packageSourceMappings. Resolves aspnet#728
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.
When package dependency versions change, the libman package feed (hosted on the azure-public ADO instance) is not writable by non-Microsoft employees. This can lead to issues building the solution when adding/updating references, especially including when runtime packages update from SDK servicing.
This change fetches any publicly available packages from nuget.org, which makes it easier to support new packages or package upgrades.
Having multiple package sources is not a risk when using packageSourceMappings.
Resolves #728