brew / rank 5451

Install cargo-release with Homebrew, apk, Nix, pacman

Cargo subcommand release: everything about releasing a rust crate. Version 1.1.3 via Homebrew; verified 2026-07-10. Also installable with nix: nix profile install nixpkgs#cargo-release.

Install command Security notes

install

Additional install commands

macOS

Homebrewverified · 100%

brew install cargo-release

local Homebrew formula metadata

Linux

Alpine Linux apkverified · 92%

sudo apk add cargo-release

Alpine Linux edge package indexes · cargo-release · source: dl-cdn.alpinelinux.org

Nixverified · 92%

nix profile install nixpkgs#cargo-release

nixpkgs package indexes · pkgs/by-name/ca/cargo-release/package.nix · source: api.github.com

Arch Linux pacmanverified · 92%

sudo pacman -S cargo-release

Arch Linux sync databases · cargo-release · source: geo.mirror.pkgbuild.com

overview

Package summary

Cargo subcommand release: everything about releasing a rust crate

Project links

Homepage

Commands and aliases

cargo-release

history

Project history and usage

cargo-release is a Cargo subcommand that wraps common Rust crate release tasks such as validation, version bumps, changelog replacements, publishing, tagging, and pushing.

Project history

The crate was first published on crates.io in March 2016, the same month the GitHub repository was created. Its README frames the tool as an extension of cargo publish with release-management defaults, while the reference documents a step-based CLI and configuration model.

Adoption history

The tool has long-running crates.io distribution, with 146 versions reported by the crates.io API and v1.1.2 current in 2026. Batch package facts list it in Homebrew, Alpine, Nix, and Arch, indicating use outside direct cargo install workflows.

How it is used

The default mode is a dry run: users run cargo release [level] to preview changes and add --execute to perform the release. The reference lists steps for changes, version, replace, hook, commit, publish, owner, tag, push, and config.

Why package nerds care

It matters to Rust package maintainers because crate releases are multi-step and easy to get subtly wrong; cargo-release centralizes version policy, workspace dependency updates, publishing, and git tagging in a reproducible Cargo-native workflow.

Timeline

2016: First crates.io release and GitHub repository creation.
2025: v0.25.x releases continued before the 1.x line.
2026: crates.io and GitHub releases reported v1.1.2 as current.

Related projects

README lists related release tools including release-pr Action, cargo-smart-release, cargo-set-version, cargo-unleash, release-plz, and cargo-workspaces.
cargo publish and git are prerequisites or delegated tools in the documented workflow.

Sources

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

narrow executable package without higher-risk signals

Signals

metadata:no-higher-risk-signals

Install behavior

No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux: ~/.config/cargo-release/release.toml
macOS: ~/Library/Application Support/cargo-release/release.toml
Unix: $CRATE/Cargo.toml ([package.metadata.release])$CRATE/release.toml$WORKSPACE/Cargo.toml ([workspace.metadata.release])$WORKSPACE/release.toml~/.release.toml
Windows: %FOLDERID_RoamingAppData%/cargo-release/release.toml

executables

Installed executables

Command	Kind	Exposure	Note
`cargo-release`	executable	indexed executable	Discovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03

manager version1.1.3

manager updated2026-07-10

local dataunknown

upstreamnot available

latest detectednot detected

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:cargo-release
Version	1.1.3
Package manager	Homebrew
Homepage	https://github.com/crate-ci/cargo-release
Repository	https://github.com/crate-ci/cargo-release
Last updated	2026-07-10T18:05:03Z
Pulse	updated
Bottle	not recorded
Service	none declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

cargo-release

nix profile install nixpkgs#cargo-release

normalized package name match
Matched by: Cargo Release

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ca/cargo-release/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

apk95%

cargo-release 1.1.3-r0

Everything about releasing a rust crate

https://github.com/crate-ci/cargo-release

sudo apk add cargo-release

License: MIT OR Apache-2.0
Architecture: x86_64
Source Package: cargo-release
1 dependencies
1 provides
normalized package name match
Matched by: Cargo Release

Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: cargo-release from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

pacman95%

cargo-release 1.1.3-1

Cargo subcommand "release": everything about releasing a rust crate