Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add an explicit NuGet source for NuGetPush
See original GitHub issueAs of NuGet client 3.4.something, performing a NuGet push requires a source to be specified (it used to use a default source if none was provided). See NuGet/Home#2504 for more information.
At first glance, I would assume this should go in NuGetPusher (https://github.com/cake-build/cake/blob/develop/src/Cake.Common/Tools/NuGet/Push/NuGetPusher.cs#L74) as an alternate branch if NuGetPushSettings.Source isn’t specified. The bigger question is probably what the default should be…
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@daveaglick re-opening this, as I have an open PR that will add documentation for this scenario.
Sounds good - I’ve already patched my own builds to supply sources on push, so this no longer affects me personally.
Anyone else who has a build script that doesn’t supply a source will break when they update NuGet and try to push. I’m guessing at this point most folks have probably already updated NuGet and encountered this if they were going to. The verbose warning should help point out what they need to do to get back up and running.