Handle patch release versions#2
Merged
Merged
Conversation
willson556
requested review from
fcheein,
mament0,
mns4595,
nehalkpatel and
thebhef
willson556
force-pushed
the
bugfix/handle-patch-release
branch
from
22f0ad7 to
48134b9
Compare
mns4595
approved these changes
Dec 17, 2025
thebhef
approved these changes
Dec 17, 2025
willson556
changed the title
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
3 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.
Description
StaflVersionclass to support optional prerelease metadata in the format:major.minor.patch+build-metadata.DS_Storeto.gitignoreto exclude macOS system files from version controlMotivation and Context
The current version regex only supports the strict format of
major.minor.patch+buildwithout any additional metadata. This change allows for prerelease tags and other metadata to be included after the build number with a hyphen separator, making the versioning system more flexible.How Has This Been Tested?
Added a new test case
test_version_patch_releasethat verifies the versioner can correctly parse and handle version strings with prerelease metadata (e.g.,1.2.3+4-dev/patch).Affected components
This change is self-contained and only affects the version parsing logic. Existing implementations that use the standard version format will continue to work as before.