-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version in code does not match that in tagged releases. #3
Comments
Fix #3 - Try to set the version number automatically
Thankyou . I will have a look. |
@vorlif yes it works for me here. thanks !! The go install github.com/vorlif/[email protected] version of course still reports as xspreak version v0.9.0, but thats cool. If you want do a tagged release of v 0.11.0 and then go of for it or just leave it. The go install from source reports version as xspreak version (devel), which is correct. |
Thank you. If you install the latest version, the correct version number will be displayed:
|
the version is hardcoded but the tagged release does not match.
Here is where we hard code the version number.
https://github.com/vorlif/xspreak/blob/15a5c7eddac3fdc55e0550308581516aee9c491e/commands/root.go#L24C18-L24C18
Below it shows the wrong version number..
common thing but annoying ..
So maybe just write a makefile target to do both so it does not happen again.
It would create the tag at the same time as updating the version that is hardcoded in the golang code.
ok I see your doing it in CI at https://github.com/vorlif/xspreak/blob/main/.github/workflows/release.yml
so modify this to do a sed update of that golang version line then ?
The text was updated successfully, but these errors were encountered: