chore: Configure Renovate - autoclosed

[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)
• .github/workflows/test.yaml (github-actions)
• renovate.json (renovate-config-presets)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• 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 (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Disable automerging feature - wait for humans to merge all PRs.
• Upgrade to unstable versions only if the existing version is unstable.
• Raise PRs immediately (after branch is created).
• Separate major versions of dependencies into individual branches/PRs.
• Separate each major version of dependencies into individual branches/PRs.
• Upgrade Docker tags to newer versions.
• Update _VERSION variables in Dockerfiles.
• Update _VERSION environment variables in GitHub Action files.
• Run Renovate on following schedule: * 7-8,18-20 * * 1-5

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

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

chore(deps): update rust crate anyhow to v1.0.100

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/anyhow-1.x-lockfile
• Merge into: main
• Upgrade anyhow to 1.0.100

chore(deps): update rust crate clap to v4.5.53

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/clap-4.x-lockfile
• Merge into: main
• Upgrade clap to 4.5.53

chore(deps): update rust crate serde_json to v1.0.145

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/serde_json-1.x-lockfile
• Merge into: main
• Upgrade serde_json to 1.0.145

chore(deps): update rust crate thiserror to v2.0.17

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/thiserror-2.x-lockfile
• Merge into: main
• Upgrade thiserror to 2.0.17

chore(deps): update rust crate time to v0.3.44

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/time-0.x-lockfile
• Merge into: main
• Upgrade time to 0.3.44

chore(deps): update rust crate humantime to v2.3.0

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/humantime-2.x-lockfile
• Merge into: main
• Upgrade humantime to 2.3.0

chore(deps): update actions/checkout action to v5

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to v5

chore(deps): update actions/checkout action to v6

• Schedule: ["* 7-8,18-20 * * 1-5"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: main
• Upgrade actions/checkout to v6

---

❓ 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 was generated by Mend Renovate. View the repository job log.