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 #28

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

Configure Renovate #28

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 8, 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/build.yml (github-actions)
  • .github/workflows/coverage.yml (github-actions)
  • .github/workflows/deploy.yml (github-actions)
  • .github/workflows/docs-pr.yml (github-actions)
  • .github/workflows/docs-publish.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • requirements-dev.txt (pip_requirements)
  • requirements.txt (pip_requirements)
  • setup.py (pip_setup)

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.

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

Update dependency Sphinx to ~=4.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx-4.x
  • Merge into: master
  • Upgrade Sphinx to ~=4.5.0
Update dependency docutils to v0.21.2
  • Schedule: ["at any time"]
  • Branch name: renovate/docutils-0.x
  • Merge into: master
  • Upgrade docutils to ==0.21.2
Update dependency m2r to ~=0.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/m2r-0.x
  • Merge into: master
  • Upgrade m2r to ~=0.3.1
Update dependency requests to ~=2.32.3
  • Schedule: ["at any time"]
  • Branch name: renovate/requests-2.x
  • Merge into: master
  • Upgrade requests to ~=2.32.3
Update dependency responses to ~=0.25.3
  • Schedule: ["at any time"]
  • Branch name: renovate/responses-0.x
  • Merge into: master
  • Upgrade responses to ~=0.25.3
Update dependency sphinx-rtd-theme to ~=1.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx-rtd-theme-1.x
  • Merge into: master
  • Upgrade sphinx-rtd-theme to ~=1.3.0
Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to v4
Update actions/setup-python action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-python-5.x
  • Merge into: master
  • Upgrade actions/setup-python to v5
Update actions/upload-artifact action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: master
  • Upgrade actions/upload-artifact to v4
Update codecov/codecov-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/codecov-codecov-action-4.x
  • Merge into: master
  • Upgrade codecov/codecov-action to v4
Update dependency Sphinx to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx-7.x
  • Merge into: master
  • Upgrade Sphinx to ~=7.4.7
Update dependency mistune to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/mistune-3.x
  • Merge into: master
  • Upgrade mistune to ==3.0.2
Update dependency sphinx-rtd-theme to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx-rtd-theme-2.x
  • Merge into: master
  • Upgrade sphinx-rtd-theme to ~=2.0.0

🚸 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/configure branch from 882e074 to 8a4f451 Compare April 3, 2023 14:36
@codecov
Copy link

codecov bot commented Apr 3, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b5ead78) 87.31% compared to head (14af2e0) 87.31%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   87.31%   87.31%           
=======================================
  Files           7        7           
  Lines         946      946           
=======================================
  Hits          826      826           
  Misses        120      120           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/configure branch from 8a4f451 to 14af2e0 Compare December 15, 2023 17:44
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