Repository navigation
CI: Exempt lockfile maintenance from Renovate release age - #192
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Lock-file maintenance rule renovate.json |
A package rule matches lockFileMaintenance updates and sets minimumReleaseAge to 0 days. |
Priority:
Estimated code review effort: 2 (Simple) | ~5 minutes
Change: Other
Possibly related issues
- aristanetworks/python-aristaproto#188: This issue tracks the pending lock-file maintenance update affected by the new age rule.
Possibly related PRs
- aristanetworks/python-aristaproto#185: This PR introduced the global seven-day minimum release age and lock-file maintenance updates that the new rule adjusts.
Merge Risk: 
Minimal · up to 15518
-
No merge-blocking risk was identified in the configuration change.
Pre-merge checks: 
5
-
Full details: Title check
-
Explanation
The title "CI: Exempt lockfile maintenance from Renovate release age" matches the single change in the PR. The only modified file, renovate.json, adds a package rule that sets minimumReleaseAge to 0 days for lockFileMaintenance updates. The title names the change, the affected update type, and the setting being bypassed. It is specific and concise, with a clear CI prefix. The PR objectives confirm the same intent.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
|



Exempt lockfile-maintenance updates from Renovate's global seven-day release-age check by setting
minimumReleaseAge: "0 days"for that update type.Maintenance updates have no package release timestamp to age against. uv already enforces the rolling seven-day cutoff through
tool.uv.exclude-newer, including transitive dependencies. Ordinary Renovate updates retain the global release-age rule, and the weekly maintenance schedule is unchanged.Only
renovate.jsonchanges. Validation runs in GitHub CI; Renovate's next maintenance run must confirm the bot behavior.Summary by CodeRabbit