Deploy releases to SonatypeOSS (staging repo) instead of Bintray #182
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
This commit switches the target of GA release deployments from Bintray to Sonatype OSS / Maven Central (triggering the creation of a staging repository, but not the closure and promotion of said repository). This will ensure releases can be performed past Bintray's sunset. Since Maven Central requires signed artifacts, the `signing` plugin is added to the mix. As a core Gradle plugin, it is trusted enough to have access to the relevant secrets. This change also relies on the `release` environment in GitHub having additional secrets (GPG signing key+passphrase, Sonatype credentials).
simonbasle
added
type/chore
violetagg
approved these changes
Mar 26, 2021
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.
This commit switches the target of GA release deployments from Bintray
to Sonatype OSS / Maven Central (triggering the creation of a staging
repository, but not the closure and promotion of said repository).
This will ensure releases can be performed past Bintray's sunset.
Since Maven Central requires signed artifacts, the
signingplugin isadded to the mix. As a core Gradle plugin, it is trusted enough to have
access to the relevant secrets.
This change also relies on the
releaseenvironment in GitHub havingadditional secrets (GPG signing key+passphrase, Sonatype credentials).