We have been working on improving the package submission workflow to reduce the overall time it takes to publish the package (right from package push/upload) till it's available for consumption and search.
As mentioned on our blog post, the package availability gets degraded multi fold whenever there is a large number package uploads/updates by a single owner that clogs the package submission pipeline. Until we are able to scale to handle the large submission rate, in the short-term, we plan to reduce the rate limits for package pushes or deletes (unlist) per user.
The current documented rate limits will be updated to the following new limits once implemented. This change will go live, soon (within a week or two):
Package Push and Unlist
API
Limit Type
Limit Value
API usecase
PUT/api/v2/package
API Key
100 / minute250 / hour
Upload a new NuGet package (version) via v2 push endpoint
We have been working on improving the package submission workflow to reduce the overall time it takes to publish the package (right from package push/upload) till it's available for consumption and search.
As mentioned on our blog post, the package availability gets degraded multi fold whenever there is a large number package uploads/updates by a single owner that clogs the package submission pipeline. Until we are able to scale to handle the large submission rate, in the short-term, we plan to reduce the rate limits for package pushes or deletes (unlist) per user.
The current documented rate limits will be updated to the following new limits once implemented. This change will go live, soon (within a week or two):
Package Push and Unlist
/api/v2/package100 / minute250 / hour/api/v2/package/{id}/{version}100 / minute50 / hour