Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Aug 7, 2025

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

  • .github/workflows/generate.yaml (github-actions)
  • package.json (npm)
  • 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.
  • 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
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Rate limit PR creation to a maximum of four per hour.
  • Rebase existing PRs any time the base branch has been updated.
  • Use semantic prefixes for commit messages and PR titles.
  • If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
  • Run Renovate on following schedule: * 0-3 * * 1

🔡 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 5 Pull Requests:

chore(deps): update dependency node to v22.21.1
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/node-22.x
  • Merge into: main
  • Upgrade node to 22.21.1
chore(deps): update dependency openapi-to-postmanv2 to v5.8.0
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/openapi-to-postmanv2-5.x-lockfile
  • Merge into: main
  • Upgrade openapi-to-postmanv2 to 5.8.0
chore(deps): update actions/checkout action to v6
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/setup-node action to v6
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update dependency node to v24
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24.12.0

🚸 Branch creation will be limited to maximum 4 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 added the dependencies label Aug 7, 2025
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