Support tagging to automatically release version to Maven Central #3
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.
I released version
1.0.0
manually via the Sonatype Nexus UI. This process involves finding the "staging" repository that is created when publishing artifacts via branch/main builds and "closing" it, which results in the artifact being deployed to Maven Central. They couldn't have made that process more confusing if they tried, and I pity the next person who has to do this.The goal of this PR is to automatically complete the process of closing/releasing the staging repository when this repo is tagged using the
tag.sh
script.