cargo-binstall 0.13.2 failed to install cargo-watch

[taiki-e]

cargo-binstall 0.13.2 failed to install cargo-watch with the following error:

05:14:15 [INFO] Resolving package: 'cargo-watch'
05:14:16 [INFO] The package will be downloaded from github.com
05:14:16 [INFO] This will install the following binaries:
05:14:16 [INFO]   - cargo-watch (cargo-watch -> /home/runner/.cargo/bin/cargo-watch-v8.1.2)
05:14:16 [INFO]   - cargo-watch (cargo-watch -> /home/runner/.cargo/bin/cargo-watch-v8.1.2)
05:14:16 [INFO] And create (or update) the following symlinks:
05:14:16 [INFO]   - cargo-watch (/home/runner/.cargo/bin/cargo-watch -> cargo-watch-v8.1.2)
05:14:16 [INFO]   - cargo-watch (/home/runner/.cargo/bin/cargo-watch -> cargo-watch-v8.1.2)
05:14:16 [INFO] Installing binaries...
Error: 05:14:16 [ERROR] Fatal error:
binstall::binfile

  × bin file /home/runner/.cargo/bin/cargo-binstallDqdKr7/bin-cargo-watch-
  │ x86_64-unknown-linux-gnu-GhCrateMeta/cargo-watch-v8.1.2-x86_64-unknown-
  │ linux-gnu/cargo-watch not found

full logs:
cargo-binstall 0.13.1 (passed): https://github.com/taiki-e/install-action/actions/runs/3117118429/jobs/5055540606
cargo-binstall 0.13.2 (failed): https://github.com/taiki-e/install-action/actions/runs/3117122909/jobs/5055549681

This was originally found in taiki-e/install-action#21, but I can confirm that this problem occurs locally as well.

[NobodyXu]

Let me perform a bisect to see which commit caused this issue.

[NobodyXu]

As expected, this bug is caused by #413 .

[NobodyXu]

I think this bug might be related to https://gitlab.com/crates.rs/cargo_toml/-/merge_requests/15

[NobodyXu]

The problem seems to be that cargo-binstall thinks there is two cargo-watch...

[NobodyXu]

I've updated PR https://gitlab.com/crates.rs/cargo_toml/-/merge_requests/15 and it should fixed this issue.
Would also add some test cases.

[NobodyXu]

cargo-binstall v0.13.2 and binstalk v0.2.0 is now yanked.

[NobodyXu]

@taiki-e cargo-binstall v0.13.3 has released, which fixed this issue.
We have re-added cargo-watch to our CI to ensure no regression.