Add nuget.config to ADO yml #217
Merged
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
|
I might need some additional context on this. Won’t customers run into problems if we ship a package to nuget.org that depends on a package in some alternate feed? |
|
We won't publish to nuget.org until all dependencies are there. This change is to allow us to stage all our packages in our ADO feed ahead of time, then release them in one go. We can look into enforcing this later, right now it will be a checklist.
repeat above to Nuget.org. |
cgillum
approved these changes
Oct 16, 2023
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.
We are now depending on some packages from other ADO feeds as we stage our releases. This change unblocks the release build for those packages.