Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support tagging to automatically release version to Maven Central #3

Merged
merged 1 commit into from
Oct 17, 2023

Conversation

jbaldassari
Copy link
Contributor

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.

@jbaldassari jbaldassari requested a review from a team October 16, 2023 14:59
- uses: actions/checkout@v3
- uses: actions/setup-java@v3
with:
java-version: '8.x'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

8.x 👀

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this is for maximum compatibility with downstream dependencies, some of which still support anything >= 8.

@jbaldassari jbaldassari merged commit 2ec3ced into main Oct 17, 2023
1 check passed
@jbaldassari jbaldassari deleted the release-on-tag branch October 17, 2023 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants