cargo-package

cargo package [options]

cargo package creates a distributable `.crate` archive from the source code. The archive is placed in `target/package/` and contains the source files, a normalized Cargo.toml, and optionally the Cargo.lock file. By default, the package is verified by extracting and building it in a temporary directory.During packaging, the Cargo.toml manifest is normalized: workspace inheritance is resolved, `[patch]`, `[replace]`, and `[workspace]` sections are removed, and path dependencies must include a version key. The `include` and `exclude` fields in Cargo.toml control which files are packaged. This command is equivalent to `cargo publish --dry-run` and is useful for inspecting what would be uploaded to a registry.

-l, --list

List files that would be included

Skip extraction and build verification

Allow uncommitted VCS changes

Ignore warnings about missing metadata

Don't include Cargo.lock

Build for target platform (verification)

Package specific workspace member

Package all workspace members

Verbose output

The Cargo.toml is normalized:- [patch], [replace], [workspace] sections removed- Path dependencies require version key- Cargo.lock included by default

Use include/exclude fields in Cargo.toml to control packaged files.

crates.io has 10MB size limit. Path dependencies without version keys are not allowed. Equivalent to cargo publish --dry-run.

cargo(1), cargo-publish(1)

Source code · Documentation