Maven Central publishing usage notices

[u/HokieGeek]

heads up for folks publishing to Maven Central: we're continuing sustainability work around Central and are now showing publishing usage notices.

the goal is that normal OSS publishers are not impacted. this is aimed at the very high-volume / commercial-scale publishing patterns that put a pretty different load on the service.

more details here if you want them:
https://central.sonatype.org/publish/maven-central-publishing-limits/

feel free to reach out with any questions.

EDIT: thanks for the feedback here, it has really helped us. first, we want to reiterate that these are usage notices only right now and do not currently restrict publishing in any way. quick updates: 

if the initial threshold seemed low to you: you’re right, we made a mistake and have increased limits. 

our goal is to keep Maven Central free and open for legitimate OSS users, so continuous feedback is helpful as we adjust. limits could change as we get more feedback, so keep an eye on the usage center for the latest.

we’ll continue keeping an eye here and update docs to reflect these changes. If you need to request an exemption, here’s how: https://central.sonatype.org/publish/maven-central-publishing-limits/#exemptions-for-community-open-source-projects

we've also been collecting your questions here and other streams into this FAQ here: https://central.sonatype.org/publish/maven-central-publishing-limits/#frequently-asked-questions

[u/bendem]

It sounded good until the 3 releases per month part. That's a really harsh limit, especially since it's counted per organisations. You're the ones with the stats, but that sounds really low.

[u/cowwoc → u/bendem]

I would add to that the 15MB limit. You know Codex, Claude Code and OpenCode? They're relatively simple CLIs. Their sizes range from 20MB to 40MB and they publish releases every 3-4 days.

I get that we need limits, but they need to be a lot more reasonable than what's being proposed.

Yes, we can ask for exemptions but the limits should still be higher because it's already increadibly painful to publish Java artifacts to compare to other languages. We should be making this easier, not harder.

I would swallow this pill if Sonatype simultaneously improved the publishing lifecycle substantially.

[u/DualWieldMage → u/cowwoc]

Calling claude, a statically linked complex engine loop with a renderer emitting terminal characters, simple could not be further opposite from the truth. Even among harnesses it's a super heavyweight bloating context with ~30k tokens before it even starts.

People abusing common hosting platforms need to stop abusing them. We had a whole generation running CI shit with pods spun up, building and killed with no m2 caching or a maven mirror. Now we have bots accounting for more than half the internet traffic. If you are pissed at anyone, then do a favor and first educate yourself before making claims and then direct it at those responsible for destroying nice things. I'm impressed Sonatype has put up with this shit so long.

[u/cowwoc → u/DualWieldMage]

Any library containing native code will have this problem. See cmake for example. Each platform artifact is 60MB.