Set the crate version centrally via the workspace

[aumetra]

No description provided.

[chipshort]

Much nicer. I think the devtools/set_version.sh also needs updating (or we just remove it and update the wiki page for publishing)

[webmaster128]

I think the devtools/set_version.sh also needs updating (or we just remove it and update the wiki page for publishing)

What happens to the internal versions that use = right now? See the dependencies in check/Cargo.toml.

[chipshort]

Good point, we do need to keep the version script for those.

[aumetra]

Tbh the entire release process could be streamlined with cargo-release.

It automatically:

• bumps all the versions across the workspace (it also keeps locked versions, i.e. =[version], as locked versions)
• creates Git tags for each crate in the workspace
• publishes the crates to crates.io

https://github.com/crate-ci/cargo-release

[chipshort]

Haven't used cargo-release before, but after trying it out, it looks pretty good. Switching to it would be fine from my side.
If we want to use the tagging feature, we need to update the changelog before running cargo release (see https://github.com/CosmWasm/cosmwasm/wiki/Releasing). Also, we would want to specify something like tag-name = "v{{version}}" to keep the current tag naming.

It would also solve some edge cases the current script has. For example, the script could replace versions of unrelated dependencies that just happen to be the same as our old version.

[aumetra]

I'm gonna have a look at integrating it. Gonna do that in a separate PR

Because having the entire release process in one, plus edge case avoidance, feels like a pretty worthwhile addition

[aumetra]

@chipshort Mind giving this a last quick look so we can merge this?

[chipshort]

LGTM
The version script will be broken with this merged, but that will become irrelevant with #2090