You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this issue we add a new Makefile command release-tag which will create a new git release tag.
The command uses the version string found in version.go to ensure consistency. It will also ensure that the new version string is SemVer compliant.
During the execution of the GitHub release workflow the git tag should be compared to the version string produced by the release-tag make command to ensure consistency.
We should implement this work in a sufficiently general way so that we can use it in our other repositories/projects.
This work will require minimal documentation in relation to version strings. So we should close #715 in favour of this issue.
The text was updated successfully, but these errors were encountered:
// These constants define the application version and follow the semantic
// versioning 2.0.0 spec (http://semver.org/).
const (
// AppMajor defines the major version of this binary.
AppMajor uint = 0
// AppMinor defines the minor version of this binary.
AppMinor uint = 17
// AppPatch defines the application patch for this binary.
AppPatch uint = 0
AppStatus = "beta"
// AppPreRelease MUST only contain characters from
// the semantic versioning spec.
// AppPreRelease MUST only contain characters from
// the semantic versioning spec.
AppPreRelease = "rc1"
GitTagIncludeStatus = true
In this issue we add a new
Makefile
commandrelease-tag
which will create a new git release tag.The command uses the version string found in
version.go
to ensure consistency. It will also ensure that the new version string is SemVer compliant.During the execution of the GitHub release workflow the git tag should be compared to the version string produced by the
release-tag
make command to ensure consistency.We should implement this work in a sufficiently general way so that we can use it in our other repositories/projects.
This work will require minimal documentation in relation to version strings. So we should close #715 in favour of this issue.
The text was updated successfully, but these errors were encountered: