Skip to content

Comments

chore: Configure Renovate#1

Merged
so1ve merged 1 commit intomainfrom
renovate/configure
Jan 9, 2026
Merged

chore: Configure Renovate#1
so1ve merged 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 9, 2026

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)
  • 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.
  • Show all Merge Confidence badges for pull requests.
  • Use semantic prefixes for commit messages and PR titles.
  • 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 GitHub.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
  • Use curated list of recommended non-monorepo package groupings.
  • Group known monorepo packages together.
  • Use Ray's Best Practice configuration from so1ve/renovate-config
  • Create a Dependency Dashboard as Issue, listing all upgrades
  • Open new PRs automatically. You can manually trigger PRs from the Dependency Dashboard, those will be opened once renovate runs again (once every hour)
  • Label all PRs with renovate
  • Use semantic commit messages for all upgrades
  • Open a maximum of 10 PRs concurrently
  • Automatically set reviewers from CODEOWNERS

🔡 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 1 Pull Request:

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

@renovate renovate bot added the renovate label Jan 9, 2026
@coderabbitai
Copy link

coderabbitai bot commented Jan 9, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@so1ve so1ve merged commit 6db4d33 into main Jan 9, 2026
@renovate renovate bot deleted the renovate/configure branch January 9, 2026 23:29
@github-actions github-actions bot mentioned this pull request Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant