Skip to content

Configure Renovate - #9

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

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

Conversation

@renovate

@renovate renovate Bot commented Jul 26, 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

  • .github/workflows/jekyll-gh-pages.yml (github-actions)
  • renovate.json (renovate-config)

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.
  • 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
  • Groups minor and patch updates together in a single PR, and treat NPM 0.x.x updates as major updates.
  • Run Renovate on following schedule: before 07:00 on Thursday

What to Expect

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

Update actions/checkout digest to 11d5960
  • Schedule: ["before 07:00 on Thursday"]
  • Branch name: renovate/actions-checkout-digest
  • Merge into: main
  • Upgrade actions/checkout to 11d5960a326750d5838078e36cf38b85af677262
Update actions/checkout action to v7
  • Schedule: ["before 07:00 on Thursday"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: main
  • Upgrade actions/checkout to 3d3c42e5aac5ba805825da76410c181273ba90b1
Update actions/configure-pages action to v6
  • Schedule: ["before 07:00 on Thursday"]
  • Branch name: renovate/actions-configure-pages-6.x
  • Merge into: main
  • Upgrade actions/configure-pages to 45bfe0192ca1faeb007ade9deae92b16b8254a0d
Update actions/upload-pages-artifact action to v5
  • Schedule: ["before 07:00 on Thursday"]
  • Branch name: renovate/actions-upload-pages-artifact-5.x
  • Merge into: main
  • Upgrade actions/upload-pages-artifact to fc324d3547104276b827a68afc52ff2a11cc49c9

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

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