-
Notifications
You must be signed in to change notification settings - Fork 15
Home
A.J. Stein edited this page Apr 18, 2023
·
5 revisions
- Ensure the
origin
remote is this repository, not a fork. - Ensure
develop
branch has all the change commits for the the release you make. - Rebase
develop
branch onmain
to ensure future linear commit history:git develop && git pull -r origin main
. - Run the maven to prepare the release:
git checkout develop && mvn -Prelease release:clean release:prepare
. - Once this is complete, sync remote state so
develop
will be pointing to the latest snapshot release and the new release tag (not a GitHub release yet):git checkout develop && git push --follow-tags
- Once the tagged version is completed for the associated release, merge the tag and release prep into
main
branch to finish the release:git checkout main && git merge --ff-only v0x.y.z && git push origin HEAD
. - Release automation in GitHub Actions will the build the snapshot release and final release in GitHub Actions.
- Once complete review the appropriate release in Sonatype OSS repository and close it to prepare for promotion.
- Once steps complete, promote the closed release with the release action.
- Go to the releases section and create the release notes based on the new
0x.y.z
tag. - Ensure
develop
branch is based offmain
for linear commits on future releases:git checkout develop && git pull -r origin main
.