cargo-artifact-dependency

Stable crate alternative for cargo artifact dependency.

[!WARNING] This crate currently only supports binary artifacts. If you need other artifact types, please open an issue on github.

Why

Cargo artifact dependencies are still an unstable Cargo feature and may still have bugs. This crate exists as a temporary alternative while artifact dependency support remains unstable.

Quick Start

use cargo_artifact_dependency::{ArtifactDependencyBuilder, BuildProfile};

fn main() -> Result<(), cargo_artifact_dependency::Error> {
    // Describe the ripgrep dependency and resolve its artifact.
    let artifact_path = ArtifactDependencyBuilder::default()
        .crate_name("ripgrep")
        .version("14")
        .bin_name("rg")
        .profile(BuildProfile::Release)
        .build()
        .unwrap()
        .resolve()?;

    // Use the resolved artifact path in your own workflow.
    println!("{}", artifact_path.display());
    Ok(())
}

Notes

This crate does not emulate Cargo.toml's full version + path dependency resolution semantics. If you need a local development path, you can gate .path(...) behind a feature.

For example:

let mut builder = ArtifactDependencyBuilder::default()
    .crate_name("example")
    .version("0.1");

#[cfg(feature = "local-dev")]
{
    builder = builder.path("/absolute/path/to/example");
}