...
| Code Block |
|---|
git push origin --tags # mvn task relies on the tag, make sure it does not collide with a branch name |
| Note |
|---|
If you are unsure whether the mvn release:perform below will succeed, you can not perform this step until after then. If the release fails due to some issue and you have pushed the tags, you will need to delete them from your workspace and from Github before re-attempting the release. |
Sonatype Release
Release the build artifacts to the Sonatype repository.
...
Push Release Branch to Maintenance
...
The release branch has changes made since code freeze. It also contains the update to the version numbers for future development.
...
Ensure that your commit history matches the release branch's commit history, except for the two additional commits.
- Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
- Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration
...
If this appears correct, you can push your release branch on to the maintenance branch.
...