Corso release version management

[ryanfkeepers]

Corso needs to track release versions, and provide those version details with the corso --version command. Whatever we use for versioning should work with https://goreleaser.com/.

Possible packages:

• https://github.com/christopherhein/go-version

[meain]

I currently have a PR at #1104 for this following the discussion on #1088 (comment) . As of now, the version shows up as the following:

With tag:    v0.0.0-ceaf04c9
Without tag: unreleased-ceaf04c9

Let me know if we should change the formats or have support for multiple formations like the package mentioned.

[meain]

#1104 was merged with the above format, let me know if it should be different. If not, we can close this issue.

[meain]

@ryanfkeepers @vkamra Let me know if the format should be changed.

[ryanfkeepers]

Do we want the tagged version to contain the SHA? In other places I've seen the following format used, and I personally found likeable:

• vM.m.p (ex: v1.2.3) for stable releases.
• vM.m.p-hash (ex: v1.2.3-ceaf04c9) for unreleased commits ahead of a stable release.

Having a stable semver should be considered an equal identifier to the hash it represents, so both in the same version tag feels a little redundant.

[meain]

The suggestion of having both version and tag came from @vkamra in #1088 (comment) . I think it makes sense to have just the v*.*.* for releases. Having the previous tag for unreleased sounds useful.

[vkamra]

Let's remove the hash from released version

[meain]

Let's remove the hash from released version

Sounds good. I'll change the version to just the tag in case of release and keep the format for unreleased.

[ryanfkeepers]

@meain @vkamra What's the possibility of adding a rolling or latest tag for unstable releases? Hashes are great, but difficult to script around. I'd be much more apt to test against the docker image if I can write myself an quick shim for things like rolling pull or rolling <corso commands>  

[vkamra]

@meain @vkamra What's the possibility of adding a rolling or latest tag for unstable releases? Hashes are great, but difficult to script around. I'd be much more apt to test against the docker image if I can write myself an quick shim for things like rolling pull or rolling <corso commands>

latest is used for the release builds. Let's use nightly to tag the latest image created off main.