NuGet version

Richard Schneider's Avatar

Richard Schneider

11 Dec, 2016 01:09 AM

My nuspec is using <package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">, so that I can tell choco about the issue tracker.

I get the following error from 'nuget pack'

Attempting to build package from 'IpfsMount.nuspec'.
The schema version of 'ipfs-mount' is incompatible with version 3.4.4.1321 of NuGet. Please upgrade NuGet to the latest version from http://go.microsoft.com/fwlink/?LinkId=213942.

Can you upgrade the build server to the latest nuget command line?

cheers

  1. Support Staff 1 Posted by Ilya Finkelshte... on 11 Dec, 2016 10:14 PM

    Ilya Finkelshteyn's Avatar

    Hi Richard,

    Yes, we will update it soon. We did hold this update because until very recent time 3.4.4. was noted as "stable" here, despite of the fact that 3.5.0 were already available.

    For now you can call this command before you using nuget:
    - appveyor DownloadFile https://dist.nuget.org/win-x86-commandline/latest/nuget.exe

    --ilya.

  2. 2 Posted by Richard Schneid... on 13 Dec, 2016 10:27 PM

    Richard Schneider's Avatar

    Thanks

  3. 3 Posted by Christian Gonza... on 06 Jun, 2017 07:38 PM

    Christian Gonzalez's Avatar

    We're running into a similar issue by not being on version 4.1. Is there a plan to upgrade soon?

    This is the build error we are getting:
    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 [email blocked] to get more details.

  4. Support Staff 4 Posted by Ilya Finkelshte... on 06 Jun, 2017 07:49 PM

    Ilya Finkelshteyn's Avatar

    Sure, we have to update, please watch this GH issue.

  5. 5 Posted by Christian Gonza... on 06 Jun, 2017 08:03 PM

    Christian Gonzalez's Avatar

    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:

    https://ci.appveyor.com/project/thomabr/sourcemap-toolkit

    My yaml file update:
    https://github.com/Microsoft/sourcemap-toolkit/commit/97c13a96d32cca1df074bc58977ac5dce20f4839

    Is there a step I’m missing?

  6. Support Staff 6 Posted by Ilya Finkelshte... on 06 Jun, 2017 08:40 PM

    Ilya Finkelshteyn's Avatar

    Appveyor nuget deployment provider does not use nuget.exe, 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.

    Also did you try to publish locally using nuget.exe and this API key? Does it work only with 4.1.0?

  7. 7 Posted by Christian Gonza... on 06 Jun, 2017 08:43 PM

    Christian Gonzalez's Avatar

    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.

  8. Support Staff 8 Posted by Ilya Finkelshte... on 06 Jun, 2017 09:03 PM

    Ilya Finkelshteyn's Avatar

    In this case to fully respect security policy, I would recommend to create custom deployment script which users exactly nuget.exe. To access artifact files from script, you can use $artifacts hashtable. For example this ($artifacts.values | Where-Object { $_.path -like '*.nupkg' })[0].path should give you local path to the first nuget package file.

    Sorry for my ignorance, could you please point me where I can set this security policy at nuget.org?

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac