cargo-publish

cargo publish [options]

cargo publish uploads a package to crates.io or another registry. It creates a `.crate` archive, verifies that the archive builds successfully, and then uploads it to the registry. Authentication is required and is typically set up via `cargo login`.Publishes are permanent and cannot be deleted or overwritten. Once a version is published, that exact version number can never be reused. The `cargo yank` command can mark a version as deprecated to prevent new projects from depending on it, but it remains available for existing users. Before publishing, ensure the version number in Cargo.toml has been incremented according to semver conventions.

--dry-run

Perform checks without uploading

Skip build verification

Allow uncommitted VCS changes

Target registry

Registry index URL

API token

Package to publish

Build target for verification

Parallel jobs

Enable features for verification

Enable all features

~/.cargo/credentials.toml

Stores API tokens for crates.io and other registries. Created by `cargo login`.

1. Create account on crates.io2. Verify email address3. Generate API token4. Run cargo login

1. Update version in Cargo.toml2. Optionally run cargo package3. Run cargo publish

Publishes are permanent. Use cargo yank to mark versions as deprecated but not delete them. Follow semver for version changes.

cargo(1), cargo-login(1), cargo-package(1), cargo-yank(1)