tag:help.appveyor.com,2012-11-13:/discussions/problems/5665-nuget-versionAppVeyor: Discussion 2018-08-25T02:17:44Ztag:help.appveyor.com,2012-11-13:Comment/414396212016-12-11T22:14:23Z2016-12-11T22:14:23ZNuGet version<div><p>Hi Richard,</p>
<p>Yes, we will update it soon. We did hold this update because
until very recent time 3.4.4. was noted as "stable" <a href="https://dist.nuget.org/index.html">here</a>, despite of the fact
that 3.5.0 were already available.</p>
<p>For now you can call this command before you using nuget:<br>
<code>- appveyor DownloadFile
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe</code></p>
<p>--ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/414396212016-12-13T22:27:33Z2016-12-13T22:27:33ZNuGet version<div><p>Thanks</p></div>Richard Schneidertag:help.appveyor.com,2012-11-13:Comment/414396212017-06-06T19:38:40Z2017-06-06T19:38:41ZNuGet version<div><p>We're running into a similar issue by not being on version 4.1. Is there a plan to upgrade soon?</p>
<p>This is the build error we are getting:<br>
Error publishing package. NuGet server returned 400: Your account requires client version '4.1.0' or higher to be able to push packages. Please contact <a href="mailto:support@nuget.org">support@nuget.org</a> to get more details.</p></div>Christian Gonzaleztag:help.appveyor.com,2012-11-13:Comment/414396212017-06-06T19:49:53Z2017-06-06T19:49:53ZNuGet version<div><p>Sure, we have to update, please watch <a href="https://github.com/appveyor/ci/issues/1590">this</a> GH issue.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/414396212017-06-06T20:03:30Z2017-06-06T20:03:31ZNuGet version<div><p>Thanks! I was trying to set my app up for downloading the latest version of Nuget.exe during the install phase, but it doesn’t seem like the NuGet deployment provider picks up that change:</p>
<p><a href="https://ci.appveyor.com/project/thomabr/sourcemap-toolkit">https://ci.appveyor.com/project/thomabr/sourcemap-toolkit</a></p>
<p>My yaml file update:<br>
<a href="https://github.com/Microsoft/sourcemap-toolkit/commit/97c13a96d32cca1df074bc58977ac5dce20f4839">https://github.com/Microsoft/sourcemap-toolkit/commit/97c13a96d32cc...</a></p>
<p>Is there a step I’m missing?</p></div>Christian Gonzaleztag:help.appveyor.com,2012-11-13:Comment/414396212017-06-06T20:40:06Z2017-06-06T20:40:06ZNuGet version<div><p>Appveyor nuget deployment provider does not use <code>nuget.exe</code>, it talks to nuget servers directly over http. I see that your nuget publishing worked OK recently. Also I see that you changed API key. Can you please provide more details about this change? Is it the new key for the same account or different account? Any other difference which can hep us to reproduce the issue would be greatly appreciated.</p>
<p>Also did you try to publish locally using <code>nuget.exe</code> and this API key? Does it work only with 4.1.0?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/414396212017-06-06T20:43:17Z2017-06-06T20:43:18ZNuGet version<div><p>Our API key was expiring. It is for the same account. We also have a new security policy that requires using the latest version of nuget.exe, which is why we get the error message.</p></div>Christian Gonzaleztag:help.appveyor.com,2012-11-13:Comment/414396212017-06-06T21:03:11Z2017-06-06T21:37:29ZNuGet version<div><p>In this case to fully respect security policy, I would recommend to create custom deployment script which users exactly <code>nuget.exe</code>. To access artifact files from script, you can use <a href="https://www.appveyor.com/docs/packaging-artifacts/#getting-information-about-uploaded-artifacts">$artifacts hashtable</a>. For example this <code>($artifacts.values | Where-Object { $_.path -like '*.nupkg' })[0].path</code> should give you local path to the first nuget package file.</p>
<p>Sorry for my ignorance, could you please point me where I can set this security policy at nuget.org?</p></div>Ilya Finkelshteyn