Configure Renovate
Metadata
Current evaluation
Renovate onboarding was closed unmerged, disabling the bot for lack of config; a Starbase-based setup later landed via #267 and commit fc1c99ad.
Resolution: closed superseded
Reason: Renovate's 2022-10-04 comment confirmed that closing the onboarding PR unmerged disabled it for lack of configuration. Merged PR #267 later added the substantive Renovate configuration in commit fc1c99ad.
Evaluated by: mr-cal-bot
No scores available.
Issue body
[](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/cla-check.yaml` (github-actions)
* `.github/workflows/release-drafter.yml` (github-actions)
* `.github/workflows/snap.yaml` (github-actions)
* `.github/workflows/spread.yaml` (github-actions)
* `.github/workflows/tests.yaml` (github-actions)
* `requirements.txt` (pip_requirements)
* `setup.cfg` (setup-cfg)
### 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 Renovate detects semantic commits, it will 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.
- A collection of workarounds for known problems with packages.
🔡 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 15 Pull Requests:
<details>
<summary>chore(deps): update dependency pydantic-yaml to v0.8.1</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/pydantic-yaml-0.x`
- Merge into: `main`
- Upgrade [pydantic-yaml](https://togithub.com/NowanIlfideme/pydantic-yaml) to `==0.8.1`
</details>
<details>
<summary>chore(deps): update dependency sphinx-autodoc-typehints to v1.19.4</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/sphinx-autodoc-typehints-1.x`
- Merge into: `main`
- Upgrade [sphinx-autodoc-typehints](https://togithub.com/tox-dev/sphinx-autodoc-typehints) to `==1.19.4`
</details>
<details>
<summary>chore(deps): update dependency certifi to v2022.9.24</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/certifi-2022.x`
- Merge into: `main`
- Upgrade [certifi](https://togithub.com/certifi/python-certifi) to `==2022.9.24`
</details>
<details>
<summary>chore(deps): update dependency docutils to v0.19</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/docutils-0.x`
- Merge into: `main`
- Upgrade docutils to `==0.19`
</details>
<details>
<summary>chore(deps): update dependency idna to v3.4</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/idna-3.x`
- Merge into: `main`
- Upgrade [idna](https://togithub.com/kjd/idna) to `==3.4`
</details>
<details>
<summary>chore(deps): update dependency mccabe to <0.7.1</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/mccabe-0.x`
- Merge into: `main`
- Upgrade [mccabe](https://togithub.com/pycqa/mccabe) to `<0.7.1`
</details>
<details>
<summary>chore(deps): update dependency pydantic to v1.10.2</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/pydantic-1.x`
- Merge into: `main`
- Upgrade [pydantic](https://togithub.com/pydantic/pydantic) to `==1.10.2`
</details>
<details>
<summary>chore(deps): update dependency pytz to v2022.4</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/pytz-2022.x`
- Merge into: `main`
- Upgrade pytz to `==2022.4`
</details>
<details>
<summary>chore(deps): update dependency sphinx to v5.2.3</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/sphinx-5.x`
- Merge into: `main`
- Upgrade [Sphinx](https://togithub.com/sphinx-doc/sphinx) to `==5.2.3`
</details>
<details>
<summary>chore(deps): update release-drafter/release-drafter action to v5.21.0</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/release-drafter-release-drafter-5.x`
- Merge into: `main`
- Upgrade [release-drafter/release-drafter](https://togithub.com/release-drafter/release-drafter) to `v5.21.0`
</details>
<details>
<summary>chore(deps): update snapcore/action-build action to v1.1.0</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/snapcore-action-build-1.x`
- Merge into: `main`
- Upgrade [snapcore/action-build](https://togithub.com/snapcore/action-build) to `v1.1.0`
</details>
<details>
<summary>chore(deps): update actions/checkout action to v3</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/actions-checkout-3.x`
- Merge into: `main`
- Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v3`
</details>
<details>
<summary>chore(deps): update actions/download-artifact action to v3</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/actions-download-artifact-3.x`
- Merge into: `main`
- Upgrade [actions/download-artifact](https://togithub.com/actions/download-artifact) to `v3`
</details>
<details>
<summary>chore(deps): update actions/setup-python action to v4</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/actions-setup-python-4.x`
- Merge into: `main`
- Upgrade [actions/setup-python](https://togithub.com/actions/setup-python) to `v4`
</details>
<details>
<summary>chore(deps): update actions/upload-artifact action to v3</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/actions-upload-artifact-3.x`
- Merge into: `main`
- Upgrade [actions/upload-artifact](https://togithub.com/actions/upload-artifact) to `v3`
</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 [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/canonical/rockcraft).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Renovate onboarding was closed unmerged, disabling the bot for lack of config; a Starbase-based setup later landed via #267 and commit fc1c99ad. | |
| stealth/space-bunny-alpha | — | closed superseded | Onboarding PR closed unmerged, disabling Renovate for lack of config. Starbase-based setup was later merged in #267 (fc1c99ad). | |
| qwen/qwen3.6-35b-a3b | — | — | The Renovate onboarding pull request was closed without merging. Dependency automation was disabled due to missing configuration, leaving the feature abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging, the Renovate onboarding setup was abandoned. Dependency automation remains disabled due to a missing configuration file. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
canonical/rockcraft#267
(confidence 99%)
Merged PR #267 implemented the Renovate configuration that the abandoned onboarding PR would have introduced.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #884 Configure Renovate | charmcraft | closed | Renovate onboarding PR #884 was closed unmerged after the bot disabled itself for lack of config; later commit 7adab896 added Renovate configuration. | |
| #162 Configure Renovate | craft-providers | closed | Renovate onboarding PR #162 was closed unmerged; the bot reported Renovate was disabled because the base branch had no configuration file. | |
| #124 Configure Renovate | craft-cli | closed | Renovate onboarding PR #124 was closed unmerged after the bot reported that Renovate was disabled because the base branch lacked a configuration file. | |
| #11 Configure Renovate | craft-store | closed | Renovate onboarding PR #11 was closed unmerged after prolonged inactivity, leaving Renovate unconfigured. Later work added Renovate config in #92 (61a215c). | |
| #289 Configure Renovate | craft-parts | closed | Renovate onboarding PR #289 was closed unmerged, leaving Renovate disabled because no configuration was added. | |
| #2 Configure Renovate | fetch-service | merged | Merged Renovate onboarding PR #2, adding renovate.json with the recommended configuration in commit 86f2a5e. | |
| #26 ci: update renovate config from starbase | craft-platforms | merged | Merged PR #26 updated Renovate configuration from starbase, landing as commit 8b2cb5d. | |
| #8 Configure Renovate - abandoned | craft-grammar | closed | Renovate onboarding PR #8 was abandoned and closed unmerged after prolonged inactivity. Its only comment said autoclosing was skipped because the branch had been modified. | |
| #617 ci: update renovate config from starbase | craft-providers | merged | Merged as commit afa0fad, updating Renovate configuration from canonical/starbase#232; the config was later replaced by starflow in #781. | |
| #268 ci: update renovate config to match starbase | craft-application | merged | Merged PR #268 in commit b9f33a53 updated Renovate configuration to match Canonical's starbase setup, changing .github/renovate.json5 (+42/-18). |