Latest version on crates.io is 0.18.0 instead of 0.19.0

[anbonifacio]

cargo install c2rust tries to install version 0.18.0 from crates.io, while the latest release on GitHub is 0.19.0.
The installation fails for me because 0.18.0 does not support Rust stable >= 1.80.

⬢ [archlinux] ❯ cargo install c2rust
    Updating crates.io index
  Installing c2rust v0.18.0

[kkysen]

Hi! We're in the process of fixing this. There were some compounding issues with cargo bugs on our pinned nightly, our pinned nightly being old and the time dependency being broken by the new 1.80 release, and updated dependencies being too new for our nightly. For now, you can just install it from git or the GitHub release. Or install c2rust 0.18 on Rust <= 1.79.

[kkysen]

We (tried to) release 0.18.0 because of the issue with the time crate type annotation, #1109. We fixed this in #1115 and started to publish 0.19.0 (we published a bunch of the crates in the workspace, but not all of them), but due to our nightly toolchain being pinned to 1.65.0, we ran into rust-lang/cargo#11148, which is fixed by rust-lang/cargo#11477, but in 1.68.0. So we need to upgrade to 1.68.0 in order to fix this. Being stuck on the old nightly is also why #1142 happened, though at least that can be easily fixed by cargo installing with --locked.

Furthermore, after tagging and releasing 0.18.0 on GitHub, #1126 was discovered, so it seemed like there was little benefit to actually publishing 0.19.0 only for it to crash on >= 1.80.0. #1126 was then fixed by #1128, but that then introduced another error, which is now finally being fixed by #1163.

Once #1163 merges, we'll try to address these issues with the old pinned nightly and then release 0.20.0 that runs without the #1126 error on Rust >= 1.80.0.

[kkysen]

• Fixed by Release 0.20.0 #1203.