Fix docs version detection for master branch builds#631
Merged
laughingman7743 merged 1 commit intomasterfrom Jan 1, 2026
Merged
Fix docs version detection for master branch builds#631laughingman7743 merged 1 commit intomasterfrom
laughingman7743 merged 1 commit intomasterfrom
Conversation
Use `git describe --tags --abbrev=0` instead of `--always` to get the latest tag without commit count suffix. This prevents the documentation from showing dev versions like "v3.21.2-2-g8d4e41c" when the master branch is pushed before its corresponding version tag is created. The issue occurred because: 1. Master branch push triggers docs build 2. Version tag is created after the push 3. git describe --always returns a dev version since no exact tag match Now the master docs will show the latest clean tag version regardless of the timing between master push and tag creation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.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
1 participant
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.
Summary
git describe --tags --abbrev=0to get the latest tag without commit count suffixProblem
When the master branch is pushed before its corresponding version tag is created, the documentation shows dev versions like
v3.21.2-2-g8d4e41c26instead of the clean versionv3.22.0.This happens because:
git describe --tags --exact-matchfails (no exact tag at HEAD yet)git describe --tags --alwaysreturns a dev version with commit countSolution
Replace
git describe --tags --alwayswithgit describe --tags --abbrev=0which returns the latest tag without the commit count suffix. This ensures master docs always show the latest clean tag version.Test Plan
make chk- all checks pass🤖 Generated with Claude Code