Installation

Install Rust and then run: shell cargo install releaser

Rust workspace release procedure

1. Read existing version from crate's toml file
2. Increment version in all workspace's crate's toml files and it's dependencies
3. Commit all version changes
4. Create new git tag
5. Run cargo publish --manifest-path …
6. Wait some time (20 seconds by default) before publish next crate so as to use new version
7. Push git tag

Rust crate release procedure

1. Read existing version from crate's toml file
2. Increment version in the toml file
3. Commit all version changes
4. Create new git tag
5. Run cargo publish --manifest-path …
6. Push git tag

Command line syntax:

``` Crate or workspace releasing tool. All crates from workspace will be released on crates.io

Usage: releaser [COMMAND]

Commands: w Release workspace specified by path c Release single crate specified by path b Create brew package manager Formula (package definition file) to publish it into a tap (MacOS and Linux only) s Create scoop package manager JSON (package definition file) to publish it into bucket (Windows only) completion Generate the autocompletion script for the specified shell help Print this message or the help of the given subcommand(s)

Options: -h, --help Print help information -V, --version Print version information Releasing workspace Release workspace specified by path

Usage: releaser w [OPTIONS]

Arguments: Version increment. One of the following: major, minor or patch [possible values: major, minor, patch] Sets workspace root path

Options: -d, --delay Delay in seconds between publish next workflow's crate [default: 20] -a, --all Whether to add option --all-features to cargo publish command -n, --noverify Whether to add option --no-verify to cargo publish command -h, --help Print help information Releasing simple crate Release single crate specified by path

Usage: releaser c [OPTIONS]

Arguments: Version increment. One of the following: major, minor or patch [possible values: major, minor, patch] Sets crate's root path

Options: -a, --all Whether to add option --all-features to cargo publish command -n, --noverify Whether to add option --no-verify to cargo publish command -h, --help Print help information Creating brew package manager Formula (package definition file) to publish it into a tap (MacOS and Linux only) Create brew package manager Formula (package definition file) to publish it into a tap (MacOS and Linux only)

Usage: releaser b [OPTIONS] --crate --base

Options: -c, --crate Sets crate's path where Cargo.toml located -l, --linux Sets Linux package directory path -m, --macos Sets Mac OS package directory path -b, --base Base URI of downloaded artifacts -u, --output [] File path to save result to. If not set result will be written into stdout -h, --help Print help information Creating scoop package manager JSON definition file to publish it into a bucket (Windows only) Create scoop package manager JSON (package definition file) to publish it into bucket (Windows only)

Usage: releaser s [OPTIONS] --crate --binary --exe --base

Options: -c, --crate Sets crate's path where Cargo.toml located -i, --binary Sets 64-bit binary package directory path -e, --exe Sets Windows executable name -b, --base Base URI of downloaded artifacts -u, --output [] File path to save result to. If not set result will be written into stdout -h, --help Print help information ```