MAN page from OpenSuSE cargo-1.52.1-6.1.i586.rpm

CARGO\-OWNER

Section: Misc. Reference Manual Pages (1)
Index

NAME

cargo-owner - Manage the owners of a crate on the registry

SYNOPSIS

cargo owner [options] --add login [crate]
cargo owner [options] --remove login [crate]
cargo owner [options] --list [crate]

DESCRIPTION

This command will modify the owners for a crate on the registry. Owners of acrate can upload new versions and yank old versions. Non-team owners can alsomodify the set of owners, so take care!

This command requires you to be authenticated with either the --token optionor using cargo-login(1).

If the crate name is not specified, it will use the package name from thecurrent directory.

See the reference <https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner> for moreinformation about owners and publishing.

OPTIONS

Owner Options

-a, --add login...

: Invite the given user or team as an owner.

-r, --remove login...

: Remove the given user or team as an owner.

-l, --list

: List owners of a crate.

--token token

: API token to use when authenticating. This overrides the token stored inthe credentials file (which is created by cargo-login(1)).
Cargo config <https://doc.rust-lang.org/cargo/reference/config.html> environment variables can beused to override the tokens stored in the credentials file. The token forcrates.io may be specified with the CARGO_REGISTRY_TOKEN environmentvariable. Tokens for other registries may be specified with environmentvariables of the form CARGO_REGISTRIES_NAME_TOKEN where NAME is the nameof the registry in all capital letters.

--index index

: The URL of the registry index to use.

--registry registry

: Name of the registry to use. Registry names are defined in Cargo configfiles <https://doc.rust-lang.org/cargo/reference/config.html>. If not specified, the default registry is used,which is defined by the registry.default config key which defaults tocrates-io.

Display Options

-v, --verbose

: Use verbose output. May be specified twice for "very verbose" output whichincludes extra output such as dependency warnings and build script output.May also be specified with the term.verboseconfig value <https://doc.rust-lang.org/cargo/reference/config.html>.

-q, --quiet

: No output printed to stdout.

--color when

Control when colored output is used. Valid values:

: •auto (default): Automatically detect if color support is available on theterminal.

: •always: Always display colors.

: •never: Never display colors.

May also be specified with the term.colorconfig value <https://doc.rust-lang.org/cargo/reference/config.html>.

Common Options

+toolchain

: If Cargo has been installed with rustup, and the first argument to cargobegins with +, it will be interpreted as a rustup toolchain name (suchas +stable or +nightly).See the rustup documentation <https://rust-lang.github.io/rustup/overrides.html>for more information about how toolchain overrides work.

-h, --help