peara
commented
1 year ago Hi, although cosmwasm-std 1.2.0 and cosmwasm-std 1.2 are the same to cargo. cosmwasm-std 1.2.1 is not.
As stated in The Cargo Book :
The string "0.1.12" is a version requirement. Although it looks like a specific version of the time crate, it actually specifies a range of versions and allows SemVer compatible updates. An update is allowed if the new version number does not modify the left-most non-zero digit in the major, minor, patch grouping. In this case, if we ran cargo update -p time, cargo should update us to version 0.1.13 if it is the latest 0.1.z release, but would not update us to 0.2.0.
I have encountered issues because of this when cosmwasm-std upgraded from 1.0.0 directly to 1.1.0 not long ago. I think to prevent this, packages should be versioned started from x.x.1 instead of x.x.0. But it seems many packages are doing that and I have not used rust long enough to understand. Anyway, another workaround is to specific the long dependency format such as: cosmwasm-std = ">=1.2.0, <1.3.0".
Please consider adding this to prevent unexpected errors.
shanev
larry0x
cosmwasm-std 1.2instead ofcosmwasm-std 1.2.0. @apollo-sturdy recently told me that these actually mean exactly the same - if you runcargo update, cargo updates the package to the latest under1.*.*regardless whether you specify the version as1or1.2or1.2.0~