[Chore] Reduce Renovate review noise#144
Conversation
roomote
Bot
requested review from
JamesRobert20,
edelauna,
hannesrudolph,
navedmerchant and
taltas
as code owners
|
No actionable issues found in the latest update. The separate major-update thread remains open intentionally because the current product direction is to rely on the normal PR and CI flow for majors. See task
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
![roomote[bot]](https://avatars.githubusercontent.com/in/2924042?s=60&v=4){kind=small}
| "schedule": ["* 21-23 * * 0"] | ||
| }, | ||
| { | ||
| "description": "Require approval before opening major React stack updates.", |
There was a problem hiding this comment.
Removing the top-level major.dependencyDashboardApproval means every non-React major update will start opening PRs immediately again. That leaves majors for the rest of the frontend/tooling/AI/actions stack ungated, which brings back the review noise this config is trying to reduce.
There was a problem hiding this comment.
Leaving this one unresolved intentionally. Per the latest product direction on this PR, major updates should open normally and rely on the usual PR/CI path rather than dashboard approval, so the broad ungated-major behavior is expected here.
edelauna
left a comment
edelauna
left a comment
There was a problem hiding this comment.
Updating renovate config to see if it helps improve dependency mgmt experience.
2 participants
What problem this solves
Reviewing dependency updates one by one is noisy in this repo, especially across AI provider SDKs and mixed frontend, tooling, and CI changes.
Running Dependabot alongside Renovate also splits dependency update ownership, and some repo-owned Node version literals had already drifted behind the current
20.20.2baseline.Why this change was made
This switches the repo to Renovate as the single updater and teaches it to group updates by operational domain instead of opening a long tail of one-off PRs.
It also aligns the remaining repo-owned Node literals to
20.20.2now, while adding regex-based managers so those versions stay in sync in future Renovate runs.User impact
Maintainers should get fewer, better-scoped dependency PRs: grouped AI/provider, frontend/UI, tooling, and GitHub Actions updates, with major updates continuing through the normal PR and CI flow and low-risk
@types/*patch updates eligible for automerge.Node version bumps should also stay consistent across package manifests, setup scripts, Dockerfiles, and GitHub Actions.