Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• Cargo.toml (cargo)
• template/Cargo.toml (cargo)
• uefi-macros/Cargo.toml (cargo)
• uefi-raw/Cargo.toml (cargo)
• uefi-services/Cargo.toml (cargo)
• uefi-test-runner/Cargo.toml (cargo)
• uefi/Cargo.toml (cargo)
• xtask/Cargo.toml (cargo)
• .github/workflows/book.yml (github-actions)
• .github/workflows/developer_productivity.yml (github-actions)
• .github/workflows/qa.yml (github-actions)
• .github/workflows/rust.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Weekly schedule on early Monday mornings.
• Run Renovate on following schedule: before 4am on Monday

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

chore(deps): update crate-ci/typos action to v1.16.22

• Schedule: ["before 4am on Monday"]
• Branch name: renovate/crate-ci-typos-1.x
• Merge into: main
• Upgrade crate-ci/typos to v1.16.22

chore(deps): lock file maintenance

• Schedule: ["before 4am on monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Mend Renovate. View repository job log here.

[nicholasbishop]

This config sets up renovate bot to:

• Run once per week
• Update Cargo.lock with the latest compatible versions. These PRs will be merged automatically if the tests pass.
• For dep updates that are already semver-compatible with the version in Cargo.toml, no changes will be made (except for the lockfile as described above). So, for example, we won't get PRs to update log-0.4.5 to 0.4.21 in Cargo.toml, because that's already semver-compat and covered by the lockfile change.
• For dep updates that are not semver-compat, a PR will be created.
• Updates of the typos action will be merged automatically if the tests pass, since that action gets updated a lot and is low-risk to merge without human oversight.

Closes #982

[phip1611]

Nice, thanks for working on this @nicholasbishop. We use Renovate internally (in conjunction with GitLab) and are quite happy with it.

[phip1611]

For the record, we currently don't update Nix/NIV dependencies automatically but this is fine, as we don't do much Nix magic at the moment. I'll update it from time to time manually, for now.