212 stable releases

new 2.2.44 Dec 5, 2023
2.2.43 Nov 30, 2023
2.2.30 Oct 31, 2023
2.1.125 Jul 22, 2023
1.0.2 Dec 12, 2022

#20 in Build Utils

Download history 187/week @ 2023-08-15 257/week @ 2023-08-22 527/week @ 2023-08-29 502/week @ 2023-09-05 463/week @ 2023-09-12 179/week @ 2023-09-19 237/week @ 2023-09-26 125/week @ 2023-10-03 48/week @ 2023-10-10 307/week @ 2023-10-17 328/week @ 2023-10-24 337/week @ 2023-10-31 243/week @ 2023-11-07 253/week @ 2023-11-14 484/week @ 2023-11-21 655/week @ 2023-11-28

1,640 downloads per month




Build Status

semantic-release-cargo integrates a cargo-based Rust project with semantic-release. This solves two use cases:

  1. publishing to crates.io, or other alternate crate registries, and
  2. compiling release binaries

Publish to crates.io

After following these instructions, you will have a semantic-release pipeline that publishes your Rust crate to crates.io.


If publishing to crates.io, you must set the CARGO_REGISTRY_TOKEN environment variable.

If publishing to an alternate registry, you must set the CARGO_REGISTRIES_<YOUR REGISTRY>_TOKEN environment variable.

This workflow is supported on the following systems:

System Supported?
macOS aarch64
macOS x64
Linux x64 gnu


Install semantic-release-cargo with npm:

$ npm install --save-dev --save-exact @semantic-release-cargo/semantic-release-cargo


Add semantic-release-cargo to your semantic-release configuration in .releaserc.json:

  "plugins": ["@semantic-release-cargo/semantic-release-cargo"]

Alternative Configuration with semantic-release-action

If you're not keen to mix npm with your Rust project, you can use the semantic-release-action.

Compile Release Binaries

After following these instructions, you will have a GitHub Actions workflow that sets the next version number in Cargo.toml and compiles your crate's release binaries.

Updating the cargo manifest with the next version number lets you reference the next version in the compiled binary, for example with the clap::crate_version macro.

The compiled binaries can be uploaded to a GitHub release using the @semantic-release/github plugin.

This workflow is supported on the following systems:

System Supported?
macOS aarch64
macOS x64
Linux aarch64
Linux x64
Linux x86


In the first job, use the next-release-version Action to save the next release version as GitHub Actions outputs:

    uses: semantic-release-action/next-release-version/.github/workflows/next-release-version.yml@v4

In the next job, use semantic-release-cargo to set the crate version before compilation:

  name: Build
  runs-on: ubuntu-latest
    - get-next-version

    - name: Checkout
      uses: actions/checkout@v3

    - name: Install semantic-release-cargo
      if: needs.get-next-version.outputs.new-release-published == 'true'
      uses: EricCrosson/install-github-release-binary@v2
        targets: semantic-release-cargo@2

    - name: Prepare semantic-release for Rust
      if: needs.get-next-version.outputs.new-release-published == 'true'
      run: semantic-release-cargo prepare ${{ needs.get-next-version.outputs.new-release-version }}

    - name: Install Rust toolchain
      uses: dtolnay/rust-toolchain@master

    - name: Cargo build
      run: cargo build --release --target=x86_64-unknown-linux-gnu --all-targets

Example Workflow

You can create a single GitHub Actions workflow that combines both use cases. This repository uses semantic-release-cargo with semantic-release to publish to crates.io and create a GitHub Release with precompiled binaries.

See release.yml for a working example.

Contributors License Agreement

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in semantic-release-cargo by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


This repository has been forked from kettleby/semantic-release-rust. All credit goes to the original author.


~258K SLoC