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
I have build a main module with dirty tree. According to 1.24 release notes:
The go build command now sets the main module’s version in the compiled binary based on the version control system tag and/or commit. A +dirty suffix will be appended if there are uncommitted changes. Use the -buildvcs=false flag to omit version control information from the binary.
You're looking at the vcs info, not the module version.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I have build a main module with dirty tree. According to 1.24 release notes:
What did you expect to see?
+dirty appended (to commit?).
What did you see instead?
I prefer the
vcs.modified
over interfering with the commit, but then the release notes are inaccurate.I also couldn't get a
vcs.tag
output even when HEAD was tagged.The text was updated successfully, but these errors were encountered: