1CARGO-OWNER(1)                                                  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           No output printed to stdout.
73
74       --color WHEN
75           Control when colored output is used. Valid values:
76
77           ·   auto (default): Automatically detect if color support is
78               available on the terminal.
79
80           ·   always: Always display colors.
81
82           ·   never: Never display colors.
83
84           May also be specified with the term.color config value
85           <https://doc.rust-lang.org/cargo/reference/config.html>.
86
87   Common Options
88       -h, --help
89           Prints help information.
90
91       -Z FLAG...
92           Unstable (nightly-only) flags to Cargo. Run cargo -Z help for
93           details.
94

ENVIRONMENT

96       See the reference
97       <https://doc.rust-lang.org/cargo/reference/environment-variables.html>
98       for details on environment variables that Cargo reads.
99

EXIT STATUS

101       0
102           Cargo succeeded.
103
104       101
105           Cargo failed to complete.
106

EXAMPLES

108        1. List owners of a package:
109
110               cargo owner --list foo
111
112        2. Invite an owner to a package:
113
114               cargo owner --add username foo
115
116        3. Remove an owner from a package:
117
118               cargo owner --remove username foo
119

SEE ALSO

121       cargo(1), cargo-login(1), cargo-publish(1)
122
123
124
125                                  2019-02-05                    CARGO-OWNER(1)
Impressum