Inject release version into drift binary#5
Merged
laulauland merged 1 commit intomainfrom Mar 26, 2026
Merged
Conversation
laulauland
force-pushed
the
lau/fix-drift-version
branch
from
57a1272 to
2d3a408
Compare
laulauland
force-pushed
the
lau/fix-drift-version
branch
from
2d3a408 to
c923f94
Compare
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
0.1.0CLI version with a build option${{ github.ref_name }}into release builds so release binaries report the release tagvX.Y.ZplaceholderNotes
The public installer/redirect flow is working correctly. The bug is that the released binary itself still prints
drift 0.1.0becausesrc/main.zighad a stale hardcoded version string.Testing
.github/workflows/release.ymlzig buildvalidation is blocked by linker issues in this environment, so GitHub CI will be the real build check