cargo owner

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 for moreinformation about owners and publishing.

OPTIONS

Owner Options

  • -a
  • —addLOGIN…​

  • Invite the given user or team as an owner.

  • -r

  • —removeLOGIN…​

  • Remove the given user or team as an owner.

  • -l

  • —list

  • List owners of a crate.

  • —tokenTOKEN

  • API token to use when authenticating. This overrides the token stored inthe credentials file (which is created by cargo-login(1)).

Cargo config 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.

  • —indexINDEX

  • The URL of the registry index to use.

  • —registryREGISTRY

  • Name of the registry to use. Registry names are defined in Cargo config files.If not specified, the default registry is used, which is defined by theregistry.default config key which defaults to crates-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.

  • -q

  • —quiet

  • No output printed to stdout.

  • —colorWHEN

  • 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.

Common Options

  • -h
  • —help

  • Prints help information.

  • -ZFLAG…​

  • Unstable (nightly-only) flags to Cargo. Run cargo -Z help fordetails.

ENVIRONMENT

See the reference fordetails on environment variables that Cargo reads.

Exit Status

  • 0

  • Cargo succeeded.

  • 101

  • Cargo failed to complete.

EXAMPLES

  • List owners of a package:
  1. cargo owner --list foo
  • Invite an owner to a package:
  1. cargo owner --add username foo
  • Remove an owner from a package:
  1. cargo owner --remove username foo

SEE ALSO

cargo(1), cargo-login(1), cargo-publish(1)