2b3c7f61c5
Under our old versioning system, when we started a new point release, we'd tag the HEAD commit of master with a tag like `v0.16.6-dev` and our scripts would use this to generate a new version number. This required a great deal of gymnastics when producing a release and caused us to litter these -dev tags everywhere. To improve this, we change version number generation to the following strategy: 1. If the commit we are building has a tag applied to it, use that tag as the version (appending the dirty bit metadata to the version, if needed). 2. If the commit we are bulding does not have a tag applied to it, take the version from the next reachable tag, increment the patch version and then append the `-dev` pre-release tag. As part of this, we also make a slight tweek to our semver generation such that instead of `-dev<TIMESTAMP>` we use `-dev.<TIMESTAMP>` which is more in line with what semver recommends. |
||
|---|---|---|
| .. | ||
| semver.go | ||
| semver_test.go | ||