Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase rate limit for “package-created” operation #8059

Open
ProFive opened this issue Sep 17, 2024 · 1 comment
Open

Increase rate limit for “package-created” operation #8059

ProFive opened this issue Sep 17, 2024 · 1 comment

Comments

@ProFive
Copy link

ProFive commented Sep 17, 2024

I am currently working on multiple Flutter/Dart packages and need to publish more than 12 packages in a day. My use case requires me to publish 4-5 additional packages beyond the current rate limit.

Request:
Could you please increase the rate limit for package creation to accommodate my use case? A higher limit would be beneficial as I'm actively working on several packages in parallel.

Use Case:
I am working on a project that involves multiple interconnected packages, and the current rate limit of 12 packages per day is too restrictive. An increase to allow for 4-5 more package creations per day would help me continue development without interruptions.

Steps to Reproduce:

  1. Create 12 packages within a 24-hour period.
  2. Attempt to create additional packages.
  3. Receive the error mentioned above.

Thank you for considering this request. Let me know if more details are needed.

@isoos
Copy link
Collaborator

isoos commented Sep 17, 2024

package-created is applied to when publishing the first version of a newly created package (note: subsequent version publishing is on a different rate limit). The main reason behind that is to prevent spamming the service and our users, but we also don't want to encourage fragmentations like putting every small method in its own package.

Could you please elaborate more on your packages, and why you need sustained publishing of new packages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants