docs: record tag-driven release automation decision#130
Draft
OmarAlJarrah wants to merge 1 commit into
Draft
Conversation
This file contains hidden or 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
1 participant
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.
Summary
Records the release-automation approach for the SDK ahead of the first non-alpha tag, in
docs/release-automation.md.The repository already has a complete, centralized publishing setup: the
dexpace.published-moduleconvention plugin configures thelibraryMaven publication, shared POM, and CI-gated in-memory PGP signing for the nine publishable modules, with coordinates sourced fromgradle.properties. What was missing was a trigger and a credential path.Decision
Tag-driven publishing through GitHub Actions, built directly on the existing
maven-publish+signingconvention plugin:v*tag push triggers a release workflow that builds, signs, and publishes to Maven Central via Sonatype directly (upstream Gradle/Actions only, no third-party release host).gradle.propertiesremains the single version source.The doc captures the decision and rationale, the tag trigger, the four required repository secrets (
SIGNING_KEY,SIGNING_PASSWORD,SONATYPE_USERNAME,SONATYPE_PASSWORD), the publish target, the workflow steps, and an operational checklist for the first stable release.Docs-only change.
Closes #75