(main) Automate release using GH Actions #745
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.
Adds release pipeline to do relases from GitHub Action
Closes #141
Thank you for opening a pull request and contributing to asciidoctor-maven-plugin!
What kind of change does this PR introduce? (check at least one)
What is the goal of this pull request?
Automate releases to make the release process much easier, less error prone and avoid local configurations.
Note it requires:
s4u/setup-maven-action
does not work, so under-the-hood actions are used Can't commit when using 's4u/setup-maven-action' s4u/setup-maven-action#68I'll create a new GPG key only for CI, but the user used to upload to
oss.sonatype
is a token linked to my account.Are there any alternative ways to implement this?
There's an alternative plugin https://github.com/sonatype/nexus-maven-plugins/tree/main (docs https://central.sonatype.org/publish/publish-maven/), but there hasn't been release since 2016. Still maybe at some point we can review it it allows to close the staging repo automatically.
Are there any implications of this pull request? Anything a user must know?
Is it related to an existing issue?
Finally, please add a corresponding entry to CHANGELOG.adoc