Repository navigation
Makefile: describe version using only io500-*_vN tags - #123
Merged
Merged
Conversation
The build version comes from "git describe", which picks the newest annotated tag on a commit. The floating release tag (e.g. io500-sc26) is moved to each new io500-sc26_vN commit, and if it is re-tagged after io500-sc26_vN is created, the binary reports "io500-sc26" instead of the specific version that identifies the code being run. Restrict "git describe" to io500-*_vN tags so the version is always the precise release, independent of the order in which tags are made. Untagged commits still describe relative to the previous io500-*_vN tag, and --always still falls back to the commit hash. Tested by re-creating io500-sc26 as a newer annotated tag on io500-sc26_v3: the old command reports "io500-sc26", the new one "io500-sc26_v3". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gflofst
approved these changes
Oct 23, 2026
jeanbez
approved these changes
Oct 28, 2026
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
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.
The build version comes from "git describe", which picks the newest annotated tag on a commit. The floating release tag (e.g. io500-sc26) is moved to each new io500-sc26_vN commit, and if it is re-tagged after io500-sc26_vN is created, the binary reports "io500-sc26" instead of the specific version that identifies the code being run.
Restrict "git describe" to io500-_vN tags so the version is always the precise release, independent of the order in which tags are made. Untagged commits still describe relative to the previous io500-_vN tag, and --always still falls back to the commit hash.
Tested by re-creating io500-sc26 as a newer annotated tag on io500-sc26_v3: the old command reports "io500-sc26", the new one "io500-sc26_v3".