Skip to content

Latest commit

 

History

History
38 lines (30 loc) · 1.58 KB

VERSIONING.md

File metadata and controls

38 lines (30 loc) · 1.58 KB
Raw

Versioning

This project uses semantic versioning.

The patch-version (3rd digit) is bumped up automatically at every merge to master (by Travis CI).

Increment the patch version

This is done automatically by Travis CI. Nothing special to do here. Example: merging when latest tag is v3.23.291 will automaticall tag a version v3.23.292.

Increment the minor version

Since Travis CI only automatically increases the patch-version, we need to manually pre-tag with the new version we want.

Scenario:

  • actual version is v3.23.291
  • tag one of the commit on your branch with the new version you want.
    • it is important that the patch version be -1, since it will be incremented automatically by Travis CI.
    • git tag v3.24.-1 && git push --tags
  • open the pull request.
  • after merge, Travis CI will tag automatically the right final version v3.24.0.
  • delete the temporary manual tag
    • git tag -d v3.24.-1 && git push --tags

Increment the major version

Since Travis CI only automatically increases the patch-version, we need to manually pre-tag with the new version we want.

Scenario:

  • actual version is v3.23.291
  • tag one of the commit on your branch with the new version you want.
    • it is important that the patch version be -1, since it will be incremented automatically by Travis CI.
    • git tag v4.0.-1 && git push --tags
  • open the pull request.
  • after merge, Travis CI will tag automatically the right final version v4.0.0.
  • delete the temporary manual tag
    • git tag -d v4.0.-1 && git push --tags