CARGO-OWNER(1)

✨ CARGO-OWNER ✨

okay bestie, welcome to the cargo-owner era 💖 this is the General Commands Manual page for cargo-owner, and yes it's giving "I manage who gets to touch your crate" 💅 buckle up.

---

🌸 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 🦋

so like. this command modifies the owners for a crate on the registry. periodt.

what does being an owner even get you, you ask? owners of a crate can upload new versions and yank old versions. iconic, right? and here's the part where you go 😭: non-team owners can also modify the set of owners, so take care! like, for real, they can just add more people. the audacity.

this command requires you to be authenticated — either with the --token option or by using cargo-login(1).

if you don't name a crate? no stress, it'll just use the package name from the current directory 🫶

for more info about owners and publishing, go look at the reference: https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner

---

💅 OPTIONS 💅

👑 Owner Options

• -a, --add login… — invite the given user or team to be an owner. bestie acquisition arc ✨
• -r, --remove login… — remove the given user or team as an owner. it's giving "we need to talk" 💀
• -l, --list — list owners of a crate. the vibe check of "who is actually on this crate" 🌈
• --token token — API token to use when authenticating. this overrides the token stored in the credentials file (which is created by cargo-login(1)).

Cargo config environment variables can be used to override the tokens stored in the credentials file. the token for crates.io may be specified with the CARGO_REGISTRY_TOKEN environment variable. tokens for other registries may be specified with environment variables of the form CARGO_REGISTRIES_NAME_TOKEN where NAME is the name of the registry in all capital letters. (config docs: https://doc.rust-lang.org/cargo/reference/config.html)

• --index index — the URL of the registry index to use. 🔥
• --registry registry — name of the registry to use. registry names are defined in Cargo config files (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 to crates-io. 😌

🍓 Display Options

• -v, --verbose — use verbose output. may be specified twice for "very verbose" output, which includes extra output such as dependency warnings and build script output. may also be specified with the term.verbose config value (https://doc.rust-lang.org/cargo/reference/config.html). spill the tea, cargo ☕
• -q, --quiet — do not print cargo log messages. may also be specified with the term.quiet config value (https://doc.rust-lang.org/cargo/reference/config.html). silent treatment, but make it productive 🙈
• --color when — control when colored output is used. valid values:
  • auto (default): automatically detect if color support is available on the terminal.
  • always: always display colors.
  • never: never display colors.

may also be specified with the term.color config 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 cargo begins with +, it will be interpreted as a rustup toolchain name (such as +stable or +nightly). see the rustup documentation (https://rust-lang.github.io/rustup/overrides.html) for more information about how toolchain overrides work. toolchain switching, main character energy 👑
• --config KEY=VALUE or PATH — overrides a Cargo configuration value. the argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. this flag may be specified multiple times. see the command-line overrides section (https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides) for more information.
• -C PATH — changes the current working directory before executing any specified operations. this affects things like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories searched for discovering .cargo/config.toml, for example. this option must appear before the command name, for example cargo -C path/to/my-project build.

this option is only available on the nightly channel (https://doc.rust-lang.org/book/appendix-07-nightly-rust.html) and requires the -Z unstable-options flag to enable (see #10098 https://github.com/rust-lang/cargo/issues/10098). no cap, stable users cannot sit with us on this one 💀

• -h, --help — prints help information. when in doubt, ask the manual 🫶
• -Z flag — unstable (nightly-only) flags to Cargo. run cargo -Z help for details. the forbidden knowledge aisle 🔥

---

🌈 ENVIRONMENT 🌈

see the reference (https://doc.rust-lang.org/cargo/reference/environment-variables.html) for details on environment variables that Cargo reads. yes, cargo is nosy, it reads the whole group chat 💜

---

💖 EXIT STATUS 💖

• 0: Cargo succeeded. ate, left no crumbs ✨
• 101: Cargo failed to complete. it's giving tragedy 😭

---

🧚 EXAMPLES 🧚

1. List owners of a package:

cargo owner --list foo

2. Invite an owner to a package:

cargo owner --add username foo

3. Remove an owner from a package:

cargo owner --remove username foo

---

🔥 SEE ALSO 🔥

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

---

and that's the whole page bestie 🎀 from the General Commands Manual section of the docs, this has been CARGO-OWNER(1) — go forth and manage your owners responsibly, ily, mwah 💋