[Publishing] add ./gradlew publishToOssStagingIfNeeded
#2385
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add
./gradlew publishToOssStagingIfNeededlike there is./gradlew publishIfNeeded. The reason this is a separate task is that Sonatype does not support the--paralleloption (it might be specifying a profile Id but I'm not sure how to do this).Also add
publishToOssStagingIfNeededto the ci script so that Sonatype publishing is done on Github Actions starting with version 2.2.2.This PR also adds
closeAndReleaseRepositorybased on vanniktech/gradle-maven-publish-plugin#63. It makes it possible to release on Maven Central without having to log in at https://oss.sonatype.org/ and would therefore potentially make the release 100% automated.I haven't added it to the CI yet, I'll do it if it works well on
2.2.2