[PR #1] [MERGED] Configure Renovate #203

New issue

Closed

opened 2026-03-02 15:56:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 15:56:51 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/probberechts/soccerdata/pull/1
Author: @renovate[bot]
Created: 2/3/2022
Status: ✅ Merged
Merged: 2/3/2022
Merged by: @probberechts

Base: master ← Head: renovate/configure

📝 Commits (1)

c1fc7f9 Add renovate.json

📊 Changes

1 file changed (+5 additions, -0 deletions)

View changed files

➕ renovate.json (+5 -0)

📄 Description

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.yml (github-actions)
.github/workflows/release.yml (github-actions)
docs/requirements.txt (pip_requirements)
pyproject.toml (poetry)

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

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

Update dependency mypy to ^0.931

Schedule: ["at any time"]
Branch name: renovate/mypy-0.x
Merge into: master
Upgrade mypy to ^0.931

Update dependency sphinx to v4.4.0

Schedule: ["at any time"]
Branch name: renovate/sphinx-4.x
Merge into: master
Upgrade sphinx to ==4.4.0

Update dependency sphinx-click to v3.1.0

Schedule: ["at any time"]
Branch name: renovate/sphinx-click-3.x
Merge into: master
Upgrade sphinx-click to ==3.1.0

Update pypa/gh-action-pypi-publish action to v1.5.0

Schedule: ["at any time"]
Branch name: renovate/pypa-gh-action-pypi-publish-1.x
Merge into: master
Upgrade pypa/gh-action-pypi-publish to v1.5.0

Update dependency flake8-bugbear to v22

Schedule: ["at any time"]
Branch name: renovate/flake8-bugbear-22.x
Merge into: master
Upgrade flake8-bugbear to ^22.0.0

Update dependency furo to v2022

Schedule: ["at any time"]
Branch name: renovate/furo-2022.x
Merge into: master
Upgrade furo to ^2022.0.0
Upgrade furo to ==2022.1.2

Update dependency rich to v11

Schedule: ["at any time"]
Branch name: renovate/rich-11.x
Merge into: master
Upgrade rich to ^11.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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 WhiteSource Renovate. View repository job log here.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/probberechts/soccerdata/pull/1 **Author:** [@renovate[bot]](https://github.com/apps/renovate) **Created:** 2/3/2022 **Status:** ✅ Merged **Merged:** 2/3/2022 **Merged by:** [@probberechts](https://github.com/probberechts) **Base:** `master` ← **Head:** `renovate/configure` --- ### 📝 Commits (1) - [`c1fc7f9`](https://github.com/probberechts/soccerdata/commit/c1fc7f922806f6b017b383e72a0faabdaacdab55) Add renovate.json ### 📊 Changes **1 file changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `renovate.json` (+5 -0) </details> ### 📄 Description [![WhiteSource Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) Welcome to [Renovate](https://togithub.com/renovatebot/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.yml` (github-actions) * `.github/workflows/release.yml` (github-actions) * `docs/requirements.txt` (pip_requirements) * `pyproject.toml` (poetry) ### 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 <code>fix</code> for dependencies and <code>chore</code> 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 🔡 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 7 Pull Requests: <details> <summary>Update dependency mypy to ^0.931</summary> - Schedule: ["at any time"] - Branch name: `renovate/mypy-0.x` - Merge into: `master` - Upgrade [mypy](https://togithub.com/python/mypy) to `^0.931` </details> <details> <summary>Update dependency sphinx to v4.4.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/sphinx-4.x` - Merge into: `master` - Upgrade [sphinx](https://togithub.com/sphinx-doc/sphinx) to `==4.4.0` </details> <details> <summary>Update dependency sphinx-click to v3.1.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/sphinx-click-3.x` - Merge into: `master` - Upgrade [sphinx-click](https://togithub.com/stephenfin/sphinx-click) to `==3.1.0` </details> <details> <summary>Update pypa/gh-action-pypi-publish action to v1.5.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/pypa-gh-action-pypi-publish-1.x` - Merge into: `master` - Upgrade [pypa/gh-action-pypi-publish](https://togithub.com/pypa/gh-action-pypi-publish) to `v1.5.0` </details> <details> <summary>Update dependency flake8-bugbear to v22</summary> - Schedule: ["at any time"] - Branch name: `renovate/flake8-bugbear-22.x` - Merge into: `master` - Upgrade [flake8-bugbear](https://togithub.com/PyCQA/flake8-bugbear) to `^22.0.0` </details> <details> <summary>Update dependency furo to v2022</summary> - Schedule: ["at any time"] - Branch name: `renovate/furo-2022.x` - Merge into: `master` - Upgrade furo to `^2022.0.0` - Upgrade furo to `==2022.1.2` </details> <details> <summary>Update dependency rich to v11</summary> - Schedule: ["at any time"] - Branch name: `renovate/rich-11.x` - Merge into: `master` - Upgrade [rich](https://togithub.com/willmcgugan/rich) to `^11.0.0` </details> <br /> 🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for `prhourlylimit` for details. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://togithub.com/renovatebot/renovate/discussions). --- This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#github/probberechts/soccerdata). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>