Sonatype/Maven Central borked everything possible since then.

Artifacts are successfully uploaded:

> Task :initializeSonatypeStagingRepository
Created staging repository 'io.kafbat--99ad1f20-7f83-4644-a052-017efb1ce2cd' at https://ossrh-staging-api.central.sonatype.com/service/local/repositories/io.kafbat--99ad1f20-7f83-4644-a052-017efb1ce2cd/content/

However, closing a release is not possible via Gradle plugin. Also, currently supported sonatype web UI doesn't list these staging repos, so one can't verify/approve the deployment. This seems to be the result of Sonatype implementing a 'staging' layer to support old-style deployment plugins (and failed miserably as far as I can tell).

For the new API, a custom plugin has to be used according to sonatype docs. The list is quite a zoo, and besides the recommended JReleaser, there are no maintenance guarantees for the rest.

Configuring JReleaser will probably require yet another night configuring all the stages, including signing the artifacts: docs.

TODO: inspect https://github.com/vanniktech/gradle-maven-publish-plugin/

Uh oh!

Release Serde API 1.1.0 #1243

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions