Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 18, 2022

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

  • .github/workflows/ci.yaml (github-actions)
  • .github/workflows/ci_pr.yaml (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
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 10 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Fix some problems with very old Maven commons versions
  • Ignore spring cloud 1.x releases
  • Ignore web3j 5.0.0 release
  • Ignore http4s digest-based 1.x milestones
  • Use node versioning for @types/node
  • Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
  • Do not upgrade from Alpine stable to edge
  • Disable Renovate Dependency Dashboard creation
  • Autodetect whether to pin dependencies or maintain ranges
  • 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
  • Fix some problems with very old Maven commons versions
  • Ignore spring cloud 1.x releases
  • Ignore web3j 5.0.0 release
  • Ignore http4s digest-based 1.x milestones
  • Use node versioning for @types/node
  • Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
  • Do not upgrade from Alpine stable to edge
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • 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 2 Pull Requests:

Update schneegans/dynamic-badges-action action to v1.4.0
  • Schedule: ["before 6am on Sunday"]
  • Branch name: renovate/schneegans-dynamic-badges-action-1.x
  • Merge into: main
  • Upgrade schneegans/dynamic-badges-action to v1.4.0
Update actions/setup-python action to v4
  • Schedule: ["before 6am on Sunday"]
  • Branch name: renovate/actions-setup-python-4.x
  • Merge into: main
  • Upgrade actions/setup-python to v4

❓ 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 added the renovate label Jun 18, 2022
@github-actions
Copy link

github-actions bot commented Jun 18, 2022

Coverage

Coverage Report
FileStmtsMissCover
TOTAL3150100%

Tests Skipped Failures Errors Time
24 0 💤 0 ❌ 0 🔥 1.020s ⏱️

@dorsha dorsha merged commit a376588 into main Jun 20, 2022
@dorsha dorsha deleted the renovate/configure branch June 20, 2022 14:51
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.

2 participants