# Release checklist
Crates.io releases are permanent: an uploaded version cannot be overwritten.
1. Confirm the version in `Cargo.toml`, crate-level documentation, README, C
header ABI version, and `CHANGELOG.md` are consistent.
2. Confirm the intended commit is clean and record current Windows/Linux test
and benchmark reports.
3. Run the full local gate on Windows and Linux:
```text
cargo fmt --all -- --check
cargo test
cargo clippy --all-targets --all-features -- -D warnings
cargo doc --no-deps --all-features
cargo package
```
4. Inspect `cargo package --list` and test the unpacked `.crate` archive.
5. Verify the crate name, package ownership, API token scope, repository URL,
and release notes on crates.io.
6. Run `cargo publish --dry-run` from the exact release commit.
7. Publish only with explicit maintainer authorization, then tag the immutable
release commit as `v<version>`.