Skip to content

chore: Configure Renovate - #3

Merged
27Bslash6 merged 1 commit into
mainfrom
renovate/configure
Oct 3, 2026
Merged

27Bslash6 merged 1 commit into
mainfrom
renovate/configure

Conversation

@cachekit-renovate-bot

@cachekit-renovate-bot cachekit-renovate-bot Bot commented Oct 2, 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)
  • .github/workflows/ci.yml (github-actions)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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
  • Group all minor and patch updates together.
  • Pin github-action digests.
  • Use semantic prefixes for commit messages and PR titles.
  • If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
  • Scan manifests under test/, tests/ and __tests__/: config:recommended ignores them via :ignoreModulesAndTests, but test harnesses in this org carry real dependencies, and a manifest Renovate never extracts can never receive a security PR.
  • Keep Renovate's default prCreation (immediate). CI in these repositories runs on pull requests, not on renovate/* branch pushes, so a branch has no status checks until its PR exists: not-pending or status-success would wait for checks that never start, and routine PRs would never open.
  • Renovate merges automerge PRs itself (platformAutomerge false) instead of arming GitHub's native auto-merge when it opens the PR. Native auto-merge waits only for the checks a branch rule marks as required. Renovate's own merge waits until nothing has failed, every check run it can see has finished as success, skipped or neutral, and every commit status other than its own passing renovate/* ones is success. Its own failed statuses (for example a lock file that failed to update) count as red, and a PR whose only statuses are its own passing ones stays pending. Checks and statuses from review bots count too, so this does not prove that CI ran: a repository that relies on automerge should require at least one CI status check. Do not set internalChecksAsSuccess: with it, a PR whose only status is the passing release-age check reads as green before CI has started.
  • Run Renovate on following schedule: before 6am

What to Expect

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

chore(deps): update rust crate libc to v0.2.190
  • Schedule: ["before 6am"]
  • Branch name: renovate/all-minor-patch
  • Merge into: main
  • Upgrade libc to 0.2.190
chore(deps): update rust crate blake2 to 0.11
  • Schedule: ["before 6am"]
  • Branch name: renovate/blake2-0.x
  • Merge into: main
  • Upgrade blake2 to 0.11
chore(deps): update rust crate getrandom to 0.4
  • Schedule: ["before 6am"]
  • Branch name: renovate/getrandom-0.x
  • Merge into: main
  • Upgrade getrandom to 0.4

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

@27Bslash6
27Bslash6 merged commit c91b573 into main Oct 3, 2026
3 checks passed
@renovate
renovate Bot deleted the renovate/configure branch October 3, 2026 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant