mirror of
https://github.com/renovatebot/renovate.git
synced 2025-01-14 08:36:26 +00:00
29 lines
1.4 KiB
Markdown
29 lines
1.4 KiB
Markdown
---
|
|
title: Rust crates
|
|
description: Rust crates support in Renovate
|
|
---
|
|
|
|
# Automated Dependency Updates for Rust crates
|
|
|
|
Renovate supports upgrading dependencies in `Cargo.toml` files and their accompanying `Cargo.lock` checksums.
|
|
|
|
## How it works
|
|
|
|
1. Renovate searches in each repository for any `Cargo.toml` files
|
|
1. Renovate extracts existing dependencies from `[dependencies]`, `[dev-dependencies]` and `[build-dependencies]`
|
|
1. Renovate attempts to find and parse a `.cargo/config.toml` file to discover index URLs for private registries
|
|
1. Renovate resolves the dependency's version using the crates.io API or by cloning the index URL
|
|
1. If Renovate finds an update, Renovate will use `cargo update` to update both `Cargo.toml` and `Cargo.lock`
|
|
|
|
## Enabling Rust Modules Updating
|
|
|
|
Renovate updates Rust crates by default.
|
|
|
|
## Private crate registries and private Git dependencies
|
|
|
|
If any dependencies are hosted in private Git repositories, [Git Authentication for cargo](https://doc.rust-lang.org/cargo/appendix/git-authentication.html) must be set up.
|
|
|
|
If any dependencies are hosted on private crate registries (ie., not on `crates.io`), then credentials should be set up in such a way that the Git command-line is able to clone the registry index.
|
|
Third-party crate registries usually provide instructions to achieve this.
|
|
|
|
Both of these are currently only possible when running Renovate self-hosted.
|