@@ -168,17 +168,43 @@ env:
168
168
- secure : " someBASE64value"
169
169
` ` `
170
170
171
- ### Versioning
172
-
173
- This project uses [semantic versioning](https://semver.org/). The version is bumped up automatically at
174
- every merge to master (by [_Travis CI_](/.travis.yml)).
175
-
176
- To control which part of the version is bumped up, the commit message of the merge commit (including the first line
177
- of the commit message of all commits it consist of) has to include a special part.
178
- - ` major-release`: the first digit (the major version) will be incremented. Example: from `3.23.291` to `4.0.0`.
179
- - `minor-release` : the second digit (the minor version) will be incremented. Example: from `3.23.291` to `3.24.0`.
180
- - anything else not including one of the text above will result in the third digit (the patch version) to be incremented.
181
- Example : ` 3.23.291` to `3.23.292`.
171
+ ## Versioning
172
+
173
+ This project uses [semantic versioning](https://semver.org/).
174
+
175
+ The patch-version (3rd digit) is bumped up automatically at every merge to master (by [_Travis CI_](/.travis.yml)).
176
+
177
+ ### Increment the patch version
178
+ This is done automatically by _Travis CI_. Nothing special to do here. Example: merging when latest tag is ` v3.23.291`
179
+ will automaticall tag a version `v3.23.292`.
180
+
181
+ # ## Increment the minor version
182
+ Since _Travis CI_ only automatically increases the patch-version, we need to manually pre-tag with the new version we
183
+ want.
184
+
185
+ Scenario :
186
+ - actual version is `v3.23.291`
187
+ - tag one of the commit on your branch with the new version you want.
188
+ - it is **important** that the patch version be `-1`, since it will be incremented automatically by _Travis CI_.
189
+ - ` git tag v3.24.-1 && git push --tags`
190
+ - open the pull request.
191
+ - after merge, _Travis CI_ will tag automatically the right final version `v3.24.0`.
192
+ - delete the temporary manual tag
193
+ - ` git tag -d v3.24.-1 && git push --tags`
194
+
195
+ # ## Increment the major version
196
+ Since _Travis CI_ only automatically increases the patch-version, we need to manually pre-tag with the new version we
197
+ want.
198
+
199
+ Scenario :
200
+ - actual version is `v3.23.291`
201
+ - tag one of the commit on your branch with the new version you want.
202
+ - it is **important** that the patch version be `-1`, since it will be incremented automatically by _Travis CI_.
203
+ - ` git tag v4.0.-1 && git push --tags`
204
+ - open the pull request.
205
+ - after merge, _Travis CI_ will tag automatically the right final version `v4.0.0`.
206
+ - delete the temporary manual tag
207
+ - ` git tag -d v4.0.-1 && git push --tags`
182
208
183
209
184
210
# # License
0 commit comments