0.72.0 tag is not on any branches

[rossburton]

If I go to https://github.com/rust-lang/rust-bindgen/tree/v0.72.0 then I see this message:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

[finalyards]

I don't.. Does it still occur? Where do you see it?

[akauppi]

I don't see such a message.

---

EDIT: ignore the rest, thx

However.. could the v0.72.0 tag be pointing to a wrong commit, since I see this:

$ git checkout v0.72.0
rust-bindgen ((HEAD detached at v0.72.0)) $ 

$ cargo install bindgen-cli
    Updating crates.io index
  Installing bindgen-cli v0.72.1
    Updating crates.io index
     Locking 72 packages to latest compatible versions
      Adding env_logger v0.10.2 (available: v0.11.8)
    Finished `release` profile [optimized] target(s) in 0.99s
  Installing /home/ubuntu/.cargo/bin/bindgen
   Installed package `bindgen-cli v0.72.1` (executable `bindgen`)

i.e. trying to install v0.72.0 from sources brings me to 0.72.1.

Same with trying to downgrade using cargo install --version:

$ cargo install --version 0.72.0 bindgen-cli
    Updating crates.io index
  Installing bindgen-cli v0.72.0
    Updating crates.io index
     Locking 72 packages to latest compatible versions
      Adding env_logger v0.10.2 (available: v0.11.8)
    Finished `release` profile [optimized] target(s) in 0.62s
  Installing /home/ubuntu/.cargo/bin/bindgen
   Installed package `bindgen-cli v0.72.0` (executable `bindgen`)
ubuntu@rust-emb:~/rust-bindgen$ bindgen --version
bindgen 0.72.1

I suspect there's a bug in 0.72.1 vs. 0.72.0, but cannot get back to the previous version.

[rossburton]

Confirming, it does look like the commits have been pushed.

[akauppi]

Confirming, it does look like the commits have been pushed.

Thus, I presume this can be closed as complete.

In the mean time, I learned that --locked is essential, to get the right bindgen library as well:

$ cargo install --locked --version 0.72.0 bindgen-cli

[ojeda]

In my opinion, --locked is always essential (unless you know what you are doing, to avoid rogue uploads) and should be the default for Cargo -- there is a long thread about it.