Release Process - codbex/codbex-kronos GitHub Wiki

Release Process

Pre-release

Triggering the Pre-release action is useful for test & development purposes.

Note: The output artefacts (Docker images, Buildpacks and Helm charts) will be overridden by the Release action. No other release artefacts are published (*.jar, *.war, Release Notes, etc.).

Pull the latest changes:
```
git pull
```

Trigger the GitHub Pre-release action:

git tag pre1.0.0
git push origin pre1.0.0

Drop the pre-release tag

git tag -d pre5.4.0
git push --delete origin pre5.4.0

Release

Create branch for Pull Request:
```
git pull
```

Change Version for Release:

mvn versions:set -DnewVersion=0.1.0
git add .
git commit -m "version set to 0.1.0 for release"
git push

Trigger GitHub Release Action:
```
git tag v0.1.0
git push origin v0.1.0
```
Note: Check https://status.maven.org/ before triggering the release! There could be a maintenance going on during the build, if that's the case, usually the Publish packages to Maven Central step will fail with 405 Not Allowed.
Close and Release the uploaded content to Maven Central:

Login to: https://s01.oss.sonatype.org/#stagingRepositories
- Close
- Release

Change Version for Development:

mvn versions:set -DnewVersion=0.2.0-SNAPSHOT
git add .
git commit -m "version set to 0.2.0-SNAPSHOT for Development"
git push

How-to

Delete Tag:

git tag -d v1.0.0
git push --delete origin v1.0.0