Handling newer versions on crates.io

[bvssvni]

For example, the Github version contains breaking changes that are not yet released. Because of a breaking change in one of the dependencies, the library is published to crates.io with a patch update.

• The version on crates.io is newer than the version in the repo
• The dependencies on crates.io are unknown

[vignesh-sankaran]

Wouldn't the patch also be committed to the repo? So the same version would effectively be on GitHub and crates.io.