cargo-owner(1)

1CARGO-OWNER(1)              General Commands Manual             CARGO-OWNER(1)
2
3
4

NAME

6       cargo-owner — Manage the owners of a crate on the registry
7

SYNOPSIS

9       cargo owner [options] --add login [crate]
10       cargo owner [options] --remove login [crate]
11       cargo owner [options] --list [crate]
12

DESCRIPTION

14       This command will modify the owners for a crate on the registry. Owners
15       of a crate can upload new versions and yank old versions. Non-team
16       owners can also modify the set of owners, so take care!
17
18       This command requires you to be authenticated with either the --token
19       option or using cargo-login(1).
20
21       If the crate name is not specified, it will use the package name from
22       the current directory.
23
24       See the reference
25       <https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner>
26       for more information about owners and publishing.
27

OPTIONS

29   Owner Options
30       -a, --add login…
31           Invite the given user or team as an owner.
32
33       -r, --remove login…
34           Remove the given user or team as an owner.
35
36       -l, --list
37           List owners of a crate.
38
39       --token token
40           API token to use when authenticating. This overrides the token
41           stored in the credentials file (which is created by
42           cargo-login(1)).
43
44           Cargo config
45           <https://doc.rust-lang.org/cargo/reference/config.html> environment
46           variables can be used to override the tokens stored in the
47           credentials file. The token for crates.io may be specified with the
48           CARGO_REGISTRY_TOKEN environment variable. Tokens for other
49           registries may be specified with environment variables of the form
50           CARGO_REGISTRIES_NAME_TOKEN where NAME is the name of the registry
51           in all capital letters.
52
53       --index index
54           The URL of the registry index to use.
55
56       --registry registry
57           Name of the registry to use. Registry names are defined in Cargo
58           config files
59           <https://doc.rust-lang.org/cargo/reference/config.html>. If not
60           specified, the default registry is used, which is defined by the
61           registry.default config key which defaults to crates-io.
62
63   Display Options
64       -v, --verbose
65           Use verbose output. May be specified twice for “very verbose”
66           output which includes extra output such as dependency warnings and
67           build script output. May also be specified with the term.verbose
68           config value
69           <https://doc.rust-lang.org/cargo/reference/config.html>.
70
71       -q, --quiet
72           Do not print cargo log messages. May also be specified with the
73           term.quiet config value
74           <https://doc.rust-lang.org/cargo/reference/config.html>.
75
76       --color when
77           Control when colored output is used. Valid values:
78
79           •  auto (default): Automatically detect if color support is
80               available on the terminal.
81
82           •  always: Always display colors.
83
84           •  never: Never display colors.
85
86           May also be specified with the term.color config value
87           <https://doc.rust-lang.org/cargo/reference/config.html>.
88
89   Common Options
90       +toolchain
91           If Cargo has been installed with rustup, and the first argument to
92           cargo begins with +, it will be interpreted as a rustup toolchain
93           name (such as +stable or +nightly). See the rustup documentation
94           <https://rust-lang.github.io/rustup/overrides.html> for more
95           information about how toolchain overrides work.
96
97       --config KEY=VALUE or PATH
98           Overrides a Cargo configuration value. The argument should be in
99           TOML syntax of KEY=VALUE, or provided as a path to an extra
100           configuration file. This flag may be specified multiple times. See
101           the command-line overrides section
102           <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides>
103           for more information.
104
105       -C PATH
106           Changes the current working directory before executing any
107           specified operations. This affects things like where cargo looks by
108           default for the project manifest (Cargo.toml), as well as the
109           directories searched for discovering .cargo/config.toml, for
110           example. This option must appear before the command name, for
111           example cargo -C path/to/my-project build.
112
113           This option is only available on the nightly channel
114           <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and
115           requires the -Z unstable-options flag to enable (see #10098
116           <https://github.com/rust-lang/cargo/issues/10098>).
117
118       -h, --help
119           Prints help information.
120
121       -Z flag
122           Unstable (nightly-only) flags to Cargo. Run cargo -Z help for
123           details.
124

ENVIRONMENT

126       See the reference
127       <https://doc.rust-lang.org/cargo/reference/environment-variables.html>
128       for details on environment variables that Cargo reads.
129

EXIT STATUS

131       •  0: Cargo succeeded.
132
133       •  101: Cargo failed to complete.
134

EXAMPLES

136        1. List owners of a package:
137
138               cargo owner --list foo
139
140        2. Invite an owner to a package:
141
142               cargo owner --add username foo
143
144        3. Remove an owner from a package:
145
146               cargo owner --remove username foo
147