You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes. With commits 31f64b8 and 714dfbe and recently released Git v2.32.0 (annoncement) we create a file RELEASE.txt that contain GIT_COMMIT and VERSION variables. This should happen automatically when GitHub builds the release archive (I hope, not sure what Git version or implementation they use internally).
Things left doing:
Make Makefile target check if RELEASE.txt file exists and if so, use variables therein (if present) for linker flags. Otherwise use git tools (like now) to determine those values.
Finally, make a release and check if things work like expected 💯
The source releases are missing the version infos that are compiled into the binaries.
Explanation in this PR: #128
Conclusion: needs to be done with goreleaser.
The text was updated successfully, but these errors were encountered: