Handle pre-release versions - #95
Merged
Merged
Conversation
This commit updates the logic that generates package versions from Git tags. If the tag matches a semver.org pre-release with "alpha", "beta" or "rc" as the pre-release identifier, then the "-" in the version string is substituted for "~". That is, a tag like `9.0.0-beta1` becomes the following package version: `9.0.0~beta1` This is done because the `dpkg` and `rpm` package managers treat `~` specially and sort any version strings containing it before all other strings. This changes allows a `9.0.0~alpha1` package to upgrade to `9.0.0~beta1`, and then to `9.0.0~rc0`, and finally to `9.0.0`. See: https://semver.org See: https://manpages.debian.org/bookworm/dpkg-dev/deb-version.7.en.html#Sorting_algorithm See: https://rpm.org/docs/6.0.x/man/rpm-version.7#Comparing Signed-off-by: Charlie Sharpsteen <charlie@overlookinfratech.com>
bastelfreak
approved these changes
Jul 15, 2026
8 tasks
Sharpie
added a commit
to OpenVoxProject/shared-actions
that referenced
this pull request
Jul 15, 2026
PR OpenVoxProject/vanagon#95 updated Vanagon's handling of Git tags. If the tag matches a semver.org pre-release with "alpha", "beta" or "rc" as the pre-release identifier, then the "-" in the version string is substituted for "~". That is, a tag like `9.0.0-beta1` becomes the following package version: `9.0.0~beta1` This is done because the `dpkg` and `rpm` package managers treat `~` specially and sort any version strings containing it before all other strings. This changes allows a `9.0.0~alpha1` package to upgrade to `9.0.0~beta1`, and then to `9.0.0~rc0`, and finally to `9.0.0`. This commit updates the munging logic in the `build_vanagon.yml` workflow to correctly pass these versions to `rake vox:upload`. See: https://semver.org See: https://manpages.debian.org/bookworm/dpkg-dev/deb-version.7.en.html#Sorting_algorithm See: https://rpm.org/docs/6.0.x/man/rpm-version.7#Comparing Signed-off-by: Charlie Sharpsteen <charlie@overlookinfratech.com>
8 tasks
Sharpie
added a commit
to OpenVoxProject/openvox-release-infra
that referenced
this pull request
Jul 15, 2026
This commit expands the regex used to validate package versions to allow the tilde, `~`, character. The `dpkg` and `rpm` package managers use the tilde to denote a pre-release version is eligible for upgrade to a final release. PR OpenVoxProject/vanagon#95 updated Vanagon to insert the tilde in package versions in order to build SemVer tags like `9.0.0-beta1` as a package with version `9.0.0~beta1`. Signed-off-by: Charlie Sharpsteen <charlie@overlookinfratech.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Short description
This commit updates the logic that generates package versions from Git tags. If the tag matches a semver.org pre-release with "alpha", "beta" or "rc" as the pre-release identifier, then the "-" in the version string is substituted for "~". That is, a tag like
9.0.0-beta1becomes the following package version:9.0.0~beta1This is done because the
dpkgandrpmpackage managers treat~specially and sort any version strings containing it before all other strings. This changes allows a9.0.0~alpha1package to upgrade to9.0.0~beta1, and then to9.0.0~rc0, and finally to9.0.0.See: https://semver.org
See: https://manpages.debian.org/bookworm/dpkg-dev/deb-version.7.en.html#Sorting_algorithm
See: https://rpm.org/docs/6.0.x/man/rpm-version.7#Comparing
Checklist
I have:
Signed-off-byannotation to each of my commitsGenerated-byorAssisted-byannotations to each of my commits created with the help of an AI agent