Add specialized parsing function for utsname.release to std.SemanticVersion
#25019
+38
−6
Conversation
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
TibboddiT
commented
Aug 26, 2025
TibboddiT
force-pushed
the
feat-parse_utsname_release
branch
from
5d439d1 to
25f259e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some
utsname.releasevalues might not be fully semver compliant. For example, on one of my old android phones,unamereturns this release version:3.18.120-perf+(see https://github.com/torvalds/linux/blob/8f5ae30d69d7543eee0d70083daf4de8fe15d585/scripts/setlocalversion#L197-L210).This PR adds the
SemanticVersion.parseUtsnameReleasefunction which handles versions ending with a '+' without a build version, adds / updates related tests, and updatessystem.zig.resolveTargetQueryto use the specialized function when populatingos.version_rangefor relevant operating systems.