[CT-253] Standardize Pre-release Version Format

[emmyoop]

We are currently inconsistent with prerelease version format.

• Homebrew formula versions contain hyphens. (ex: 1.0.0-rc1)

• GitHub release tags + GHCR image tags + PyPi package versions don't contain hyphens (ex: 1.0.0rc1)

Per semver.org

A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.–.

Our CHANGELOG denotes prereleases without the hyphens currently but will start using the hypens once we move to changie (in progress)

We should move all versions to use hyphen for consistency. Current state works but consistency is better.

[leahwicz]

@jtcohen6 if we changed the naming convention for versions to follow this convention, would there be any consequences? Cloud wouldn't have an issue but would this mess up installs from individual users at all? It would just be a change in the prerelease naming convention from what I can tell and not major/minor/patch

[jtcohen6]

I think PyPi may not let us do this no matter what? From PEP 440:

Semantic versions containing a hyphen (pre-releases - clause 10) or a plus sign (builds - clause 11) are not compatible with this PEP and are not permitted in the public version field.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.