cargo-release alternatives and similar packages
Based on the "Cargo" category.
Alternatively, view cargo-release alternatives based on common mentions on social networks and blogs.
-
cargo-update
A cargo subcommand for checking and applying updates to installed executables -
cargo-deb
A cargo subcommand that generates Debian packages from information in Cargo.toml -
cargo-modules
A cargo plugin for showing a tree-like overview of a crate's modules. -
cargo-benchcmp
A small utility to compare Rust micro-benchmarks. -
cargo-bitbake
cargo extension that can generate BitBake recipes utilizing the classes from meta-rust -
cargo-ebuild
cargo extension that can generate ebuilds using the in-tree eclasses -
cargo-testify
Watches changes in a rust project, runs test and shows friendly notification
Static code analysis for 29 languages.
Do you think we are missing an alternative of cargo-release or a related project?
|
Less time debugging, more time building
sponsored
scoutapm.com
|
Popular Comparisons
-
cargo-releasevscargo-make
-
cargo-releasevsRustup
-
cargo-releasevsClippy
-
cargo-releasevsjust
-
cargo-releasevscargo-modules
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
cargo release
Features
- Ensure you are in a good state for release, including:
- Right branch
- Up-to-date with remote
- Clean tree
- Supports workspaces using cargo's native flags, like
--workspace,--excludeand--package- Updates dependent crates in workspace when changing version
- Change detection to help guide in what crates might not need a release
- Optionally share commits
- Handles
cargo publish, tagging, and pushing - Pre-release search and replace for custom version updates, including
- Updating changelogs
- Update tags in
Dockerfiles
- Pre-release hook for extra customization, including
Install
Current release: 0.21.1
cargo install cargo-release
Usage
cargo release [level]
- See the [reference](docs/reference.md) for more on
level, other CLI arguments, and configuration file format. - See also the [FAQ](docs/faq.md) for help in figuring out how to adapt cargo-release to your workflow.
Prerequisite
- Your project should be managed by git.
Dry run
By default, cargo-release runs in dry-run mode so you can safely run it and
verify what it will do.
- Increase the logging level with each additional
-vto get more details - Speed up dry-run by skipping
cargo-publishs verify step with--no-verify
Once you are ready, pass the --execute flag.
License
Licensed under either of
- Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT) at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
*Note that all licence references and agreements mentioned in the cargo-release README section above
are relevant to that project's source code only.