Renovate: No README updates, label behaviour change, automerge lockfiles#4953
Merged
Bibo-Joshi merged 4 commits intomasterfrom Sep 15, 2025
Merged
Renovate: No README updates, label behaviour change, automerge lockfiles#4953Bibo-Joshi merged 4 commits intomasterfrom
Bibo-Joshi merged 4 commits intomasterfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR addresses issues from #4938 by modifying the Renovate configuration to improve automated dependency management. It removes problematic README update functionality and adjusts labeling and automerge behavior.
Key changes:
- Removes automatic README version updates that were causing issues
- Changes default label from "dependencies" to "ci-cd"
- Enables automerge for lockfile maintenance PRs
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Contributor
Reconfigure PR ResultsThis is an reconfigure PR comment to help you understand and re-configure your renovate bot settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome: Detected Package Files
Configuration SummaryBased on the default config's presets, Renovate will:
What to ExpectWith your current configuration, Renovate will create 16 Pull Requests: Update astral-sh/setup-uv digest to b75a909
Update codecov/codecov-action action to v5.5.1
Update dependency astral-sh/uv to v0.8.17
Update github/codeql-action action to v3.30.3
Update Pylint to v3.3.8
Update astral-sh/setup-uv action to v6.7.0
Update Chango to v0.5.0
Update Mypy to v1.18.1
Update pre-commit hook APScheduler to ~=3.11.0
Update pre-commit hook cachetools to >=5.5.2,<5.6.0
Update pypa/gh-action-pypi-publish action to v1.13.0
Update Ruff to v0.13.0
Update actions/setup-python action to v6
Update actions/stale action to v10
Update pre-commit hook cachetools to v6
Lock file maintenance
|
Bibo-Joshi
approved these changes
Sep 15, 2025
Member
Bibo-Joshi
left a comment
There was a problem hiding this comment.
Thanks for the PR!
Maybe the aiolimiter issue is because the pre-commit config is currently not matching pyproject.toml 🤔 anyway, updating readme manually for now sounds okay.
Thanks also for the hint about the write permissions. I'll add those once I can see how this PR will affect the other open ones 😅
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tries to fix the problems in #4938.
I removed updating the READMEs for now. I think we'll just manually do it for now until we can figure out why that happened on all PRs and why was it only the APScheduler one which changed.
@Bibo-Joshi I think the other PR's didn't automerge because only you can merge to master? Maybe add an exclusion to that rule and then the other PR's will start merging?