Skip to content

Configure Renovate#1

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

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

Conversation

@renovate

@renovate renovate Bot commented Aug 27, 2025

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

  • frontend/package.json (npm)
  • pyproject.toml (pep621)
  • 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.
  • 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
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • Run lock file maintenance (updates) early Monday mornings.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Use version pinning (maintain a single version only and not SemVer ranges).
  • Do not separate patch and minor upgrades into separate PRs for the same dependency.
  • Rebase existing PRs any time the base branch has been updated.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.

What to Expect

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

Update dependency axios to v1.16.0 [SECURITY]
  • Branch name: renovate/npm-axios-vulnerability
  • Merge into: main
  • Upgrade axios to 1.16.0
Update dependency requests to v2.33.0 [SECURITY]
  • Branch name: renovate/pypi-requests-vulnerability
  • Merge into: main
  • Upgrade requests to 2.33.0
Update dependency vite to v7.3.5 [SECURITY]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: main
  • Upgrade vite to 7.3.5
Update dependency eslint-plugin-react-refresh to ^0.5.0
  • Schedule: ["after 10pm every weekday","every weekend","before 5am every weekday"]
  • Branch name: renovate/dev-dependencies
  • Merge into: main
  • Upgrade eslint-plugin-react-refresh to ^0.5.0
Update Python to >=3.14,<3.15
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: main
  • Upgrade python to >=3.14,<3.15
Update dependency crewai to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/crewai-1.x
  • Merge into: main
  • Upgrade crewai to >=1.14.6,<1.15.0
Update devDependencies (major)
Lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • 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 Aug 27, 2025
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.

0 participants