Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #3

Open
wants to merge 1 commit into
base: step1
Choose a base branch
from
Open

Configure Renovate #3

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 5, 2021

Mend Renovate

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

  • Dockerfile (dockerfile)
  • requirements.txt (pip_requirements)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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 directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Limit to maximum 10 open PRs at any time.
  • Pin dependency versions where depType=dependencies. Usually applies only to non-dev dependencies in package.json.
  • 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.
  • Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
  • Run Renovate on following schedule: before 6am on Sunday

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


What to Expect

With your current configuration, Renovate will create 1 Pull Request:

chore(deps): update python docker tag to v3.11.4
  • Schedule: ["before 6am on Sunday"]
  • Branch name: renovate/python-3.x
  • Merge into: step1
  • Upgrade python to 3.11.4-alpine

❓ 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. View repository job log here.

@renovate renovate bot force-pushed the renovate/configure branch from 01f90c3 to 1c5e211 Compare June 26, 2022 09:31
@renovate renovate bot force-pushed the renovate/configure branch from 1c5e211 to 05a60af Compare March 22, 2023 17:27
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