github package registry not compatible with dotnet nuget client

All instructions followed. Attempting to run a “dotnet nuget push”.

warn : No API Key was provided and no API Key could be found for ‘https://nuget.pkg.github.com/ORGANIZATION’. To save an API Key for a source use the ‘setApiKey’ command.

info : Pushing PACKAGE.nupkg to ‘https://nuget.pkg.github.com/ORGANIZATION’…

info :   PUT https://nuget.pkg.github.com/ORGANIZATION/

info : An error was encountered when fetching ‘PUT https://nuget.pkg.github.com/ORGANIZATION/’. The request will now be retried.

info : An error occurred while sending the request.

info :   The response ended prematurely.

10 Likes

Hi @gustavdw,

Thank you for being here!  Unfortunately, at present - we only support the documented build tools and clients, in this case nuget.

I will however pass this back as a feature request, and this is something we are exploring going forwards - as each of these package formats support a wide range of build tools and clients beyond the ‘default’ option.

Keep an eye on our documentation and https://github.blog/changelog for updates.

1 Like

Any updates on this? It’s quite a significant blocker.

4 Likes

There is a workaround using curl here https://github.com/NuGet/Home/issues/8580#issuecomment-555696372, at least until GitHub fixes problem of not allowing the apiToken to work directly using the nuget push command.

2 Likes

@andreagriffiths11, I’m not sure if you read the original message. @gustavdw specifically said “All instructions followed.”

I also am attempting to use this feature, exactly as documented here, and getting exactly the same error message. I’ve tried both with dotnet nuget push and regular nuget push.

Unfortunately, the error / incorrect documentation make this feature a non-starter for my company as well.

2 Likes

@andreagriffiths11 Month later, issue still exists without any update from your end…

Hey Friends,

My sincere apologies for the delay on update here. This issue should now be resolved, please let us know if you are still having any problems. 

To try out bundling and publishing the package using the dotnet cli: 

Here’s a guide on how to configure this: https://gist.github.com/Mattamorphic/4e2ff8f62f8e2bc7f04f9d2a91bc722d

Your personal access token will need to have repo, package:read and package:write scopes: dotnet tool install gpr -g --version 0.1.13-beta gpr push path/to/your.nupkg -k <token> gpr list -k <token>.

3 Likes

Same error. Still doesn’t work. 

1 Like

I got it to work using gpr, but the help doc says to use dotnet nuget which still does not work.