Has anyone had any issues publishing their librari...

# feed

[Juan Hurtado]

Has anyone had any issues publishing their libraries to Maven Central due to rate limits?

[Mark Murphy]

that would seem like a more appropriate question for #C8C4JTXR7

and note that there is a long thread over there already on the Maven Central rate limits

[Juan Hurtado]

Thanks Mark. For anyone else who finds this thread while struggling with the new Maven Central limits:
In the meantime, a solid workaround is using the vanniktech/gradle-maven-publish-plugin to filter out redundant checksums and reduce file count. For the long-term KMP-specific fix, JetBrains is tracking the investigation via KT-87203

[Kirill Grouchnikov]

Right now the limits are informational and not enforced. If you have issues publishing, it is not because of these upcoming limits.

[Juan Hurtado]

to clarify: publishToMavenLocal is fine for all modules. My problem was on Central — only some artifacts published; the namespace was at ~96% file usage, so I thought it might be limit-related. i wonder what should i check for partial Central publishes 🤔

[Kirill Grouchnikov]

I've had suboptimal experience with publishing (via the github.com/vanniktech/gradle-maven-publish-plugin, but I didn't dig deeper to see if it was the plugin or the backend) when org.gradle.parallel was set to true in gradle.properties. In most cases it ended up publishing 2 or more separate "bundles" to the Sonatype backend.