Add `--token` to `cargo info`

[marcoieni]

Problem

cargo publish allow to pass --token <TOKEN> to authenticate.
I was expecting cargo info to support the same, so that it can used with private registries as well.

Proposed Solution

Allow authenticating using --token in cargo info.

Notes

I'm interested in this because I want to use cargo info PACKAGE@VERSION in release-plz to programmatically detect if a package is published.
At the moment I use the crates-index crate for that but I would like to get rid of this dependency and simplify my code.

[epage]

Allow authenticating using --token in cargo info.

FYI we deprecated cargo login <token> in #15057. Looks like we overlooked cargo publish --token and should deprecate that as well

I'm interested in this because I want to use cargo info PACKAGE@VERSION in release-plz to programmatically detect if a package is published.

Note that cargo info is a human-focused command, and not programmatic focused, and there are very few compatibility guarantees around its behavior.

[marcoieni]

Looks like we overlooked cargo publish --token and should deprecate that as well

I'm glad my issue was useful in some way 😅

Note that cargo info is a human-focused command, and not programmatic focused, and there are very few compatibility guarantees around its behavior.

thanks for the heads up! But I'm not parsing stdout, I'm just checking if status is success.
This is the only way I found to verify if a package is published via the cargo cli.

Anyway, it seems there's no interest in this so feel free to close the issue, thanks!

[epage]

thanks for the heads up! But I'm not parsing stdout, I'm just checking if status is success.
This is the only way I found to verify if a package is published via the cargo cli.

It is valid in these cases to turn an error status into a success status.