I’ve narrowed down the issue.

I’m testing with the same repository, same code, same state. On each test, I’m incrementing the Nuget version of my package. Sometimes it succeeds in pushing to GPR, but most of the time it fails to push the new package.

Pushing to nuget.org has never been a problem in my tests, Pushing to github.com sometimes works, but mostly fails.

image899×949 59.4 KB

image1043×947 49.3 KB

image879×186 10.2 KB

So what exactly is going on here?

In my case, the answer has been most of the time in the content of the PackageReleaseNotes tag, by using characters like (, ), ' has caused the publication of the package failed.

Thanks for the tip. However I removed the PackageReleaseNotes tag now and it’s still only working once in a whiile.

I have enabled diagnostic output and can see that the workflow actually pulls the github.token from the workflow, so authentication should also not be an issue.

Successful push:

image835×554 31.6 KB

Failed push:

image1195×549 21.8 KB

image1145×453 21.1 KB

I also tried swapping the Github/Nuget push but the workflow still fails on PushGithub most of the time.

Thanks for the response.

I’ve tried using nuget.exe instead. It has run a first time and made a successful push. I’ll need to try some more pushes to draw a definite conclusion.

I have to note however that I’ve got a similar setup with a pure .NET Standard project, and this project has never given a problem building and pushing to nuget and GPR. I suspect that the issue is introduced when publishing a multi-target nuget package (I have no clue what could possibly cause this).

I’ll keep you up-to-date if using nuget.exe works consistently.

(6/6 successful pushes)

The chance of a dotnet nuget push failing seems to increase with the size of the package (but it’s still somewhat random).

Here is an example that shows pushes of various sized packages:

jcansdale-test/nuget-push-test

Contribute to jcansdale-test/nuget-push-test development by creating an account on GitHub.

By the time we get to a 2049 kB package, the push is almost certain to fail!

Interesting finding. I never had a problem pushing a .NET Standard nuget package to github.com/nuget.org. The problem started occuring by creating a multi-target nuget package. This implies that for each target, there’s a DLL in the package and increases the size of the package drastically.

But how come the package can successfully be pushed to nuget.org all the time, while it fails for github.com, using the same command?

Anyhow, using nuget.exe seems to work reliably. Thanks for the help.

But how come the package can successfully be pushed to nuget.org all the time, while it fails for github.com, using the same command?

It’s probably something to do with GitHub’s load balancer and they way chunked encoding works. The team will hopefully be digging into it soon!

This definitely has something to do with the size of the package. I have smaller packages that upload without issue but bigger ones fail with the above error message. It’s really really inconvenient and frustrating.

It’s really really inconvenient and frustrating.

I’ve written a GitHub Action based on https://github.com/jcansdale/gpr that you should find works consistently.

You can use it like this:

    - uses: jcansdale/gpr@v0.1.257
      with:
        command: push
        path: **/*.nupkg

Please let me know if you try it!

Great! Thanks. I’ll check this out.

Hi, thanks for this Github Action. Just note that if you build a dotnet package whit --include-symbols then it will upload each package two times and complain that its allready uploaded second time it gets uploaded.

I replaced dotnet nuget by @jcansdale tool for working with the GitHub Package Registry and it works like a charm:

      - name: Install tool for working with the GPR
        run: dotnet tool install -g gpr
  - name: Publish Package
    run: |
      gpr push PATH-TO-PKG-FILE.nupkg

Hello, we are seeing this issue with Nuget packages < 50 KB in size. It would be nice to avoid having to use the gpr push workaround. Do we know what the root cause for this failure is when using dotnet nuget push? There are no commas in my package description.

Hi @mtttcgcg,

Hello, we are seeing this issue with Nuget packages < 50 KB in size. It would be nice to avoid having to use the gpr push workaround. Do we know what the root cause for this failure is when using dotnet nuget push?

If you use the dotnet nuget push --api-key <PAT> option, you should find pushes work consistently. We don’t know what the root cause for this failure was, but it appears to be somehow authentication related. You can continue using nuget.config for downloading packages. This failure was only an issue for pushes.

I hope that helps!