|
1 | 1 | # Release
|
2 | 2 |
|
3 |
| -This repository uses fully automated release process. The release build is triggered by pushing a release tag e.g. |
4 |
| -`git tag release-1 && git push origin release-1` (`1` is a sequence number to trigger the release). |
5 |
| -The release version is supplied from the |
6 |
| -[Hypertrace version plugin](https://github.com/hypertrace/hypertrace-gradle-version-settings-plugin) |
7 |
| -that uses git history and [semantic versioning settings](./semantic-build-versioning.gradle) to |
8 |
| -decide what the next release version should be. |
9 |
| - |
10 |
| -The major version is incremented if commit history contains: |
11 |
| -* Prefix `BREAKING CHANGE` |
12 |
| -* Feature suffix `!` e.g. `feat!` or `feat(scope)!` |
| 3 | +This repository uses automated release process. The release build is triggered by pushing a release tag e.g. |
| 4 | +`git tag 0.2.0 && git push origin 0.2.0` to release version `0.2.0`. |
13 | 5 |
|
14 |
| -The minor version is incremented if commit history contains: |
15 |
| -* `feat` or `feat(scope)` |
16 |
| - |
17 |
| -The patch version is incremented in other cases. |
| 6 | +The version is supplied from the |
| 7 | +[Hypertrace version plugin](https://github.com/hypertrace/hypertrace-gradle-version-settings-plugin) |
| 8 | +that uses git history (e.g. the latest tag) to derive the version. For instance if the last |
| 9 | +commit has a tag then the version from tag is used. If the last commit does not have a tag then |
| 10 | +the last tag version with `-SNAPSHOT` is used. |
18 | 11 |
|
19 |
| -## Print the next release version: |
| 12 | +## Print the current version: |
20 | 13 |
|
21 | 14 | ```bash
|
22 |
| -./gradlew printVersion -Prelease |
| 15 | +./gradlew printVersion # -Prelease - prints the next release version, it's not used at the moment. |
23 | 16 | ```
|
24 | 17 |
|
25 | 18 | ## Release CI job
|
|
0 commit comments