Skip to content
This repository has been archived by the owner on Oct 13, 2024. It is now read-only.

build: Configure Renovate #2

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

build: Configure Renovate #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 29, 2023

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

  • .gitmodules (git-submodules)
  • .github/workflows/CI.yml (github-actions)
  • .github/workflows/codeql.yml (github-actions)
  • .github/workflows/common-lint.yml (github-actions)
  • .github/workflows/issues.yml (github-actions)
  • .github/workflows/localize.yml (github-actions)
  • .github/workflows/release-notifier.yml (github-actions)
  • .github/workflows/update-changelog.yml (github-actions)
  • .github/workflows/update-docs.yml (github-actions)
  • requirements-dev.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 (except for nuget) 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.
  • Use curated list of recommended non-monorepo package groupings.
  • Default renovate configuration for LizardByte repositories
  • Renovate onboarding preset for use with LizardByte's repos
  • Run Renovate on following schedule: after 1am,before 6am

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

chore(deps): bump third-party/repo-scripts digest to 401cff8
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/third-party-repo-scripts-digest
  • Merge into: master
  • Upgrade third-party/repo-scripts to 401cff888608b3fbd7aaedc898dab50f2fd55d15
chore(deps): bump dependency flake8 to v7.1.1
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/flake8-7-x
  • Merge into: master
  • Upgrade flake8 to ==7.1.1
chore(deps): bump dependency kodi-addon-checker to v0.0.34
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/kodi-addon-checker-0-x
  • Merge into: master
  • Upgrade kodi-addon-checker to ==0.0.34
chore(deps): bump dependency pytest to v8.3.3
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/pytest-8-x
  • Merge into: master
  • Upgrade pytest to ==8.3.3
chore(deps): bump dependency pyyaml to v6.0.2
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/pyyaml-6-x
  • Merge into: master
  • Upgrade PyYAML to ==6.0.2
chore(deps): bump dependency babel to v2.16.0
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/babel-2-x
  • Merge into: master
  • Upgrade Babel to ==2.16.0
chore(deps): bump dependency furo to v2024.8.6
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/furo-2024-x
  • Merge into: master
  • Upgrade furo to ==2024.8.6
chore(deps): bump dependency lxml to v5.3.0
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/lxml-5-x
  • Merge into: master
  • Upgrade lxml to ==5.3.0
chore(deps): bump dependency numpydoc to v1.8.0
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/numpydoc-1-x
  • Merge into: master
  • Upgrade numpydoc to ==1.8.0
chore(deps): bump dependency sphinx to v7.4.7
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/sphinx-7-x
  • Merge into: master
  • Upgrade Sphinx to ==7.4.7
chore(deps): bump dependency sphinx to v8
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/sphinx-8-x
  • Merge into: master
  • Upgrade Sphinx to ==8.0.2
chore(deps): bump peter-evans/create-pull-request action to v7
  • Schedule: ["after 1am","before 6am"]
  • Branch name: renovate/peter-evans-create-pull-request-7-x
  • Merge into: master
  • Upgrade peter-evans/create-pull-request to v7

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

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 29, 2023
Copy link

codecov bot commented Dec 29, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.96%. Comparing base (72e3919) to head (d1a54e1).
Report is 80 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   81.96%   81.96%           
=======================================
  Files          11       11           
  Lines         316      316           
=======================================
  Hits          259      259           
  Misses         57       57           

@ReenigneArcher ReenigneArcher marked this pull request as draft December 29, 2023 04:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants