-
Notifications
You must be signed in to change notification settings - Fork 14
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
Implement --version
command
#456
Comments
Hey team! Please add your planning poker estimate with Zenhub @b-yap @bogdanS98 @ebma @gianfra-t |
This ticket also entails updating our version numbers in all |
Mmhh, I did not think about this. Just thought that the version number could just be the version of the runtime. But that would not really be correct... Then it probably makes sense to track the version of the client in the |
I think the current |
Yes, that would make sense. |
As far as I know, our node binaries also already support the |
Okay, so the right solution would just be to add the workflow that for every client release we actively bump the version and nothing else would need to be done here .... |
Ensure that the node clients return the version number, see this message from a third party collator:
The text was updated successfully, but these errors were encountered: