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.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 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.

---

Detected Package Files

• Cargo.toml (cargo)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/release-plz.yml (github-actions)

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.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs

---

What to Expect

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

Update Rust crate async-trait to v0.1.91

• Schedule: ["at any time"]
• Branch name: renovate/async-trait-0.x-lockfile
• Merge into: main
• Upgrade async-trait to 0.1.91

Update Rust crate futures-util to v0.3.33

• Schedule: ["at any time"]
• Branch name: renovate/rust-futures-monorepo
• Merge into: main
• Upgrade futures-util to 0.3.33

Update Rust crate serde_json to v1.0.151

• Schedule: ["at any time"]
• Branch name: renovate/serde_json-1.x-lockfile
• Merge into: main
• Upgrade serde_json to 1.0.151

Update Rust crate tar to v0.4.46

• Schedule: ["at any time"]
• Branch name: renovate/tar-0.x-lockfile
• Merge into: main
• Upgrade tar to 0.4.46

Update Rust crate thiserror to v2.0.19

• Schedule: ["at any time"]
• Branch name: renovate/thiserror-2.x-lockfile
• Merge into: main
• Upgrade thiserror to 2.0.19

Update Rust crate tracing-subscriber to v0.3.23

• Schedule: ["at any time"]
• Branch name: renovate/tokio-tracing-monorepo
• Merge into: main
• Upgrade tracing-subscriber to 0.3.23

Update Rust crate bollard to 0.21

• Schedule: ["at any time"]
• Branch name: renovate/bollard-0.x
• Merge into: main
• Upgrade bollard to 0.21

Update Rust crate oci-client to 0.17

• Schedule: ["at any time"]
• Branch name: renovate/oci-client-0.x
• Merge into: main
• Upgrade oci-client to 0.17

Update Rust crate oci-spec to 0.10.0

• Schedule: ["at any time"]
• Branch name: renovate/oci-spec-0.x
• Merge into: main
• Upgrade oci-spec to 0.10.0

Update Rust crate ocipkg to 0.4.0

• Schedule: ["at any time"]
• Branch name: renovate/ocipkg-0.x
• Merge into: main
• Upgrade ocipkg to 0.4.0

Update Rust crate rand to 0.10

• Schedule: ["at any time"]
• Branch name: renovate/rand-0.x
• Merge into: main
• Upgrade rand to 0.10

Update Rust crate rand_distr to 0.6

• Schedule: ["at any time"]
• Branch name: renovate/rand_distr-0.x
• Merge into: main
• Upgrade rand_distr to 0.6

Update Rust crate sha2 to 0.11

• Schedule: ["at any time"]
• Branch name: renovate/sha2-0.x
• Merge into: main
• Upgrade sha2 to 0.11

Update Rust crate tempfile to v3.27.0

• Schedule: ["at any time"]
• Branch name: renovate/tempfile-3.x-lockfile
• Merge into: main
• Upgrade tempfile to 3.27.0

Update Rust crate tokio to v1.53.1

• Schedule: ["at any time"]
• Branch name: renovate/tokio-1.x-lockfile
• Merge into: main
• Upgrade tokio to 1.53.1

Update actions/checkout action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-7.x
• Merge into: main
• Upgrade actions/checkout to v7

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

---

❓ 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.

[greptile-apps]

PR author is in the excluded authors list.