Rework how we release to central #14146
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the last release with OSSRH Staging API didn't go well we need an alternative way for future releases. We could either adopt JReleaser or one of the plugins from https://central.sonatype.org/publish/publish-portal-gradle/#alternatives or build our own solution.
To publish to central we first publish to a local maven repository named
ReleaseRepo
usingpublishAllPublicationToReleaseRepoRepository
then we zip that repository usinggenerateReleaseBundle
(these 2 were tested when fixing the 2.17.0 release) and finally upload it withuploadReleaseBundle
(this one is untested). We could test by failing the build at the end ofuploadReleaseBundle
and check whether the uploaded bundle is valid in the publisher portal.