Repository navigation
revert(renovate): drop "uv" from enabledManagers (#149) - #151
Conversation
This reverts commit eff0428.
📝 WalkthroughWalkthroughThis PR removes the ChangesDependency Management Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
There was a problem hiding this comment.
Pull request overview
This PR reverts the Renovate org-default config change from #149 by removing the unsupported uv entry from enabledManagers, restoring downstream Renovate validation.
Changes:
- Removes
"uv"fromrenovate.json. - Keeps existing supported managers for PEP 621, pip requirements, and GitHub Actions.
| @@ -77,7 +77,6 @@ | |||
| } | |||
| ], | |||
| "enabledManagers": [ | |||
PR ReviewStatus: BUILD FAILING (3 CI checks) — single root cause. Quality of the change itself is good. Critical (must fix before merge)
Other reviewer signals
The change itselfThe one-line removal of 🤖 Generated with Claude Code |



Reverts: #149
Summary
Reverts #149, which added
"uv"toenabledManagersinrenovate.json. The added entry caused Renovate to reject the entire org-default config with a validation error on every downstream run.What broke
Renovate (v42.92.14) does not ship a manager named
uv. The homelab team verified this by inspecting the manager directory inside the running Renovate container. With"uv"inenabledManagers, Renovate emits:This rejects the entire config, not just the offending line. Every downstream repo that inherits
ByronWilliamsCPA/.github:renovate.json(homelab-infra, gleif, backpacking, williaby-claude, .claude, image-generation, reference-library, plus future repos) stopped getting Renovate updates after #149 merged.How uv projects are actually covered
PR #149 was based on a wrong mental model.
uvsupport in Renovate works as follows:uvuses the standard PEP 621[project]table inpyproject.toml. The existingpep621manager (already inenabledManagers) finds these dependencies. No separateuvmanager is needed.uv.lockis regenerated as a PR artifact by the Renovate container. This is handled inhomelab-infra/services/renovate/docker-compose.ymlviaRENOVATE_BINARY_SOURCE=install, which lets containerbase download theuvbinary at runtime. Configured in homelab-infra PR chore(deps): Update GitHub Actions #309 (merged), follow-up cleanup in PR #314.The absence of
"uv"fromenabledManagersis therefore deliberate, not an oversight.Why this trap is sticky
"uv"is intuitively the right manager name for a uv-lockfile-managed project. Two independent agents have now reached for it (the homelab team in May, and the author of #149). Without a tombstone, the next contributor will reach for it again.This PR captures the tombstone in the PR body and in the maintainer's session memory (so future Claude Code sessions on this repo will not re-suggest the same fix). A future contributor who proposes adding
"uv"toenabledManagersshould be referred to this PR.Pre-merge audit suggestion
The lookup that would have prevented #149:
Either would have surfaced PR #309 and #314 within seconds, exposing the deliberate-revert reasoning that lived in the consumer repo rather than the source repo.
Change
"enabledManagers": [ - "uv", "pep621", "pip_requirements", "github-actions" ],One-line removal. Restores the pre-#149 config.
Test plan
pre-commit run --all-files)Generated with Claude Code