Automated Dependency Updates for Cargo
Categories: rust
Renovate supports updating Cargo dependencies.
File Matching¶
By default, Renovate will check any files matching the following regular expression: (^|/)Cargo\.toml$.
For details on how to extend a manager's fileMatch value, please follow this link.
Supported datasources¶
This manager supports extracting the following datasources: crate.
Default config¶
{
"commitMessageTopic": "Rust crate {{depName}}",
"fileMatch": [
"(^|/)Cargo\\.toml$"
],
"versioning": "cargo"
}
Additional Information¶
Extracts dependencies from Cargo.toml files, and also updates Cargo.lock files too if found.
When using the default rangeStrategy=auto:
- If a "less than" instruction is found (e.g.
<2) thenrangeStrategy=widenwill be selected, - Otherwise,
rangeStrategy=update-lockfilewill be selected.
The update-lockfile default means that most upgrades will update Cargo.lock files without the need to change the value in Cargo.toml.
Private Modules Authentication¶
Before running the cargo commands to update the cargo.lock, Renovate exports git insteadOf directives in environment variables.
Renovate uses this logic before it updates any "artifacts":
The token from the hostRules entry matching hostType=github and matchHost=api.github.com is added as the default authentication for github.com.
For those running against github.com, this token will be the default platform token.
Next, all hostRules with both a token or username/password and matchHost will be fetched, except for any github.com one from above.
Rules from this list are converted to environment variable directives if they match any of these characteristics:
- No
hostTypeis defined, or hostTypeiscargo, orhostTypeis a platform (github,gitlab,azure, etc.)
Open items¶
The below list of features were current when this page was generated on November 21, 2024.