Skip to content

chore: Configure Renovate#58

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure
Open

chore: Configure Renovate#58
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Jun 8, 2026

Copy link
Copy Markdown

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)
  • Dockerfile (dockerfile)
  • .github/workflows/release.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 15 Pull Requests:

chore(deps): update rust crate time to v0.3.47 [security]
  • Branch name: renovate/crate-time-vulnerability
  • Merge into: main
  • Upgrade time to 0.3.47
chore(deps): update rust crate tokio to v1.38.2 [security]
  • Branch name: renovate/crate-tokio-vulnerability
  • Merge into: main
  • Upgrade tokio to 1.38.2
chore(deps): update rust crate hyper to v0.14.32
  • Schedule: ["at any time"]
  • Branch name: renovate/hyper-0.x-lockfile
  • Merge into: main
  • Upgrade hyper to 0.14.32
chore(deps): update rust crate lcov to v0.8.2
  • Schedule: ["at any time"]
  • Branch name: renovate/lcov-0.x-lockfile
  • Merge into: main
  • Upgrade lcov to 0.8.2
chore(deps): update rust crate serde_json to v1.0.150
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_json-1.x-lockfile
  • Merge into: main
  • Upgrade serde_json to 1.0.150
chore(deps): update rust crate thiserror to v1.0.69
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-1.x-lockfile
  • Merge into: main
  • Upgrade thiserror to 1.0.69
chore(deps): update rust-futures monorepo to v0.3.32
  • Schedule: ["at any time"]
  • Branch name: renovate/rust-futures-monorepo
  • Merge into: main
  • Upgrade futures to 0.3.32
chore(deps): update serde monorepo to v1.0.228
  • Schedule: ["at any time"]
  • Branch name: renovate/serde-monorepo
  • Merge into: main
  • Upgrade serde to 1.0.228
chore(deps): update rust crate clap to v4.6.1
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-4.x-lockfile
  • Merge into: main
  • Upgrade clap to 4.6.1
chore(deps): update rust docker tag to v1.96
  • Schedule: ["at any time"]
  • Branch name: renovate/rust-1.x
  • Merge into: main
  • Upgrade rust to 1.96
fix(deps): update rust crate itertools to 0.14.0
  • Schedule: ["at any time"]
  • Branch name: renovate/itertools-0.x
  • Merge into: main
  • Upgrade itertools to 0.14.0
fix(deps): update rust crate octocrab to 0.53.0
  • Schedule: ["at any time"]
  • Branch name: renovate/octocrab-0.x
  • Merge into: main
  • Upgrade octocrab to 0.53.0
fix(deps): update rust crate sha2 to 0.11.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sha2-0.x
  • Merge into: main
  • Upgrade sha2 to 0.11.0
fix(deps): update rust crate hyper to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/hyper-1.x
  • Merge into: main
  • Upgrade hyper to 1.0.0
fix(deps): update rust crate thiserror to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-2.x
  • Merge into: main
  • Upgrade thiserror to 2.0.0

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

@renovate renovate Bot requested a review from a team as a code owner June 8, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants