-
Notifications
You must be signed in to change notification settings - Fork 5
How to release a new version (old)
Kevin Wallimann edited this page Mar 14, 2024
·
1 revision
- Create a release branch, e.g.
release/0.5.6
- Push all changes you want to release to that release branch.
- Change the version in pom if needed. Current version without -SNAPSHOT will be used as next version (e.g. 1.0.3-SNAPSHOT will be released as 1.0.3).
- Run Hyperdrive-Trigger - Release job in TeamCity on
release/0.5.6
branch
TeamCity will
- release: create release commit and tag, and push them to release branch
- deploy: once the tag is created two jobs (for Scala 2.11 and 2.12) will be triggered that will build and deploy Abris into Maven repo.
- Go to https://oss.sonatype.org/#stagingRepositories. Find zacoabsa-.... Release or drop the artefacts.
- Merge the release branch into develop and delete the release branch.
- Merge all changes into develop.
-
git checkout -b release/<version>
, e.g.git checkout -b release/1.0.0
-
mvn -Dmanual-release -B release:prepare
Will push branch and tag to github. The version will be inferred from the current SNAPSHOT version. If you want to manually specify a version, use-DreleaseVersion=1.0.0
. This step produces a backup file ofpom.xml
and arelease.properties
file. -
git clean -f
to remove the backup files -
git checkout v<version>
. Checkout the tag -
mvn -B -e -DskipTests -Dmanual-release -Ddeploy -Dossrh clean deploy
Build project and deploy to ossrh. Deployment to ossrh may take up to 20 minutes. - Go to https://oss.sonatype.org/#stagingRepositories. Find zacoabsa-.... Release or drop the artefacts.
- Merge the release branch into develop and delete the release branch.