Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

cargo-dist review

Free#12 of 29 in Release Automation Tools

Open-source packaging and release automation for Rust applications distributing binaries and installers.

7.6/10Editor score
cargo-dist7.6 Visit cargo-dist

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

cargo-dist, now referred to as dist, is an open-source release packaging and distribution tool aimed particularly at application developers using Rust and Cargo. It suits solo developers and teams that want to turn Git-tagged versions into application binaries, archives, installers, and release announcements. Workspace-aware planning can select packages to announce, making it relevant to Cargo workspaces as well as individual applications.

The release workflow covers packaging through publication: it generates CI release workflows, builds binaries for configured platforms, creates tarballs and shell or PowerShell installers, and produces machine-readable release manifests. It can upload artifacts and create or edit GitHub Releases, with release notes drawn from a project’s RELEASES or CHANGELOG file. Package-manager publishing extends the output to Homebrew, npm, Apt, and Chocolatey; supported artifact types also include a Windows MSI. This breadth is useful when a project ships across several distribution channels, while the central workflow remains oriented around GitHub.

There is no purchase tier to compare: cargo-dist is open source and has a free plan, with self-hosted deployment and documentation and community support. Its scope is packaging and distribution, not deciding semantic version increments or generating changelogs. Projects seeking automated version calculation or changelog authoring should look elsewhere; teams that already manage those inputs and want CI to build, package, and publish tagged releases are a better fit. The project’s current name is dist, though cargo-dist remains in its repository and installer names.

cargo-dist pros and cons

  • Where it wins
    • Generates CI workflows to build and publish releases from Git tags.
    • Creates archives, installers, and machine-readable release manifests.
    • Supports GitHub Releases and package channels including Homebrew and npm.
  • Where it doesn't
    • Focuses on packaging and distribution, not semantic-version calculation.
    • Does not generate changelogs; release notes come from project files.
    • Documented release flow is GitHub-based and self-hosted.

cargo-dist fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update