Adjust release process to use tagged builds. - #472
Merged
Conversation
When tagging a commit with a version, override the build version with that tag version. Stage the release to Sonatype Central (but do not immediately publish it), and also create a .zip of all Maven artifacts for publishing to gMaven. This ensure that release artifacts can be published directly to Maven repositories from GitHub, avoiding any local modifications to edit version codes and ensuring we have clear artifact attestation for the full build chain. The GPG signing key has been added as a repository secret.
jbiral
approved these changes
Aug 18, 2026
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
2 participants
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.
When tagging a commit with a version, override the build version with that tag version. Stage the release to Sonatype Central (but do not immediately publish it), and also create a .zip of all Maven artifacts for publishing to gMaven.
This ensure that release artifacts can be published directly to Maven repositories from GitHub, avoiding any local modifications to edit version codes and ensuring we have clear artifact attestation for the full build chain.
The GPG signing key has been added as a repository secret.
See #464