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

Create an allow-list of packages that can publish more than 1000 versions #8053

Open
jonasfj opened this issue Sep 12, 2024 · 0 comments
Open

Comments

@jonasfj
Copy link
Member

jonasfj commented Sep 12, 2024

By default we limit packages to publishing at-most 1000 package versions.
This aims to:

  • Keep the size of the version listing API end-point reasonable (which would otherwise slow down pub get).
  • Mitigate abuse of the system.

However, if a package hits this limit we should have an allow-list that a package can be added to such that the limit can be increased for a specific package.

We would ask package authors to reduce the publication frequency, when they are allow-listed to published more than 1000 package versions.


Ideally, it shouldn't be necessary to publish updates more than once per week (if even that much). Obviously, there can be extenuating circumstances, if there is a serious bug, security vulnerability, etc. or perhaps you're making a big release and publishing a few quick fixes.

But in general, we don't believe that it's a good idea to publish tiny changes extremely frequently. This causes churn for all the people who depend on your package, as they will be prompted to upgrade.

If on average a package is published no more than once per week (which is extremely frequent), then back of the envelop math (1000 / 52 = 19.2) suggest that 1000 versions will be enough for 19 years of package publishing.


We should probably add a section in our documentation with guidelines around publishing frequency.

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

1 participant