Installation

Install Rust and then run:

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 [SUBCOMMAND]

OPTIONS:
    -h, --help       Print help information
    -V, --version    Print version information

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

Releasing workspace

Release workspace specified by path

USAGE:
    releaser w [OPTIONS] <INCR> <PATH>

ARGS:
    <INCR>    Version increment. One of the following: major, minor or patch [possible values:
              major, minor, patch]
    <PATH>    Sets workspace root path

OPTIONS:
    -a, --all               Whether to add option --all-features to cargo publish command
    -d, --delay <NUMBER>    Delay in seconds between publish next workflow's crate [default: 20]
    -h, --help              Print help information
    -n, --noverify          Whether to add option --no-verify to cargo publish command

Releasing simple crate

Release single crate specified by path

USAGE:
    releaser c [OPTIONS] <INCR> <PATH>

ARGS:
    <INCR>    Version increment. One of the following: major, minor or patch [possible values:
              major, minor, patch]
    <PATH>    Sets crate's root path

OPTIONS:
    -a, --all         Whether to add option --all-features to cargo publish command
    -h, --help        Print help information
    -n, --noverify    Whether to add option --no-verify to cargo publish command

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] --base <base> --crate <crate>

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

OPTIONS:
    -b, --base <base>        Base URI of downloaded artifacts
    -c, --crate <crate>      Sets crate's path where Cargo.toml located
    -l, --linux <linux>      Sets Linux package directory path
    -m, --macos <macos>      Sets Mac OS package directory path
    -u, --output <output>    File path to save result to. If not set result will be written into stdout

Creating scoop package manager JSON definition file to publish it into a bucket (Windows only)

USAGE:
    releaser s [OPTIONS] --base <base> --binary <binary> --crate <crate> --exe <exe>

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

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