Fixed buggy weaver version
output.
#399
Merged
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.
weaver version
is supposed to print out the weaver module version, something like:Previously, we used
runtime.ReadBuildInfo
to read the version of the main module. However, I realized that this version was always the string(devel)
. At first, I thought the version was(devel)
when on a non-tagged commit, but later realized that it is literally always(devel)
: golang/go#29228.I did some Googling to figure out how to print out the current module version, but it seems impossible? This PR gives up and sticks with showing the git commit. It's not as clear, but you can look up the commit in the repo history to find the module version.
@spetrovic77, I think this discovery might mean that ServiceWeaver/weaver-gke#68 is a little buggy?