Skip to content

Latest commit

 

History

History
33 lines (20 loc) · 2.02 KB

README.adoc

File metadata and controls

33 lines (20 loc) · 2.02 KB

Rust configuration

Automatic branch creation

By default, the Rust configuration does not automatically create branches (instead requiring users to manually approve dependencies in the dependency dashboard).

To enable automatic branch creation, in your repository’s renovate.json, extend from local>oxidecomputer/renovate-config//rust/autocreate after extending from the global preset. This will enable:

  • Automatic branch creation for dependencies

  • Lockfile updates every Monday morning Pacific time

Setting rangeStrategy to bump

Our configuration sets the rangeStrategy option to bump. This means that if a new version of a crate is released, the version in Cargo.toml is also bumped. This is generally desirable since new versions often have features or bugfixes that we’ll start depending on—​such that resolving to an older version would be a mistake. (But it’s reasonable to disagree, in which case you can use the update-lockfile strategy.)

Note that as of 2024-04-25 (Renovate version 37.323.1), bump is actually the default for Renovate’s Cargo backend. However, per a maintainer, the default strategy may change soon.

Using update-lockfile for x or x.y dependencies

We currently use the update-lockfile strategy for dependencies specified as x or x.y. While the bump strategy also works for those dependencies, it will cause PRs for no-op updates (example). We’re choosing to not introduce that kind of churn.

Exclusions

The following crates are currently excluded from consideration:

  • vsss-rs: Relatively delicate part of omicron (trust quorum), has shipped breakages in the past. See issue #20.

Note
If you’re excluding a new crate, be sure to add information about it to this section, including the reason(s) for exclusion.