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 Cargo.toml files, doesn't it? Is this something we should talk about @TorstenStueber? Like, when do we want to bump to new major, minor, or patch versions? Or do we want to keep this number aligned to something else?

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 Cargo.toml of the client. We would then need to define a scheme for version numbers.

I think the current node-template already has this --version flag. Not sure what it returns, but it is likely that the person was referring to this. If this is the case we should modify the client to return the same to be consistent with later versions.

Yes, that would make sense.

As far as I know, our node binaries also already support the --version flag but it's currently quite useless as we don't update the version in the Cargo.toml files which is probably the main concern of the external operators.

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 ....