chore: Add a shared quiet-by-default dependency update policy - #29
Merged
Conversation
ecv
force-pushed
the
claude/quiet-by-default-renovate
branch
2 times, most recently
from
September 9, 2026 00:14
5975545 to
0271bfe
Compare
Dependency updates open pull requests across the organization on the bot's schedule rather than ours. Sixty-one of them currently request review from a twenty-two person team, the oldest since August 2025, and they bury the pull requests people opened. This adds the policy as a preset under the name Renovate looks for when it onboards a repository, so a new repository starts quiet and an existing one can extend the same file by name. Key changes: - Add renovate-config.json holding the policy, listing updates on each repository's dependency dashboard and opening none until asked - Point this repository's own config at the preset rather than repeating the stock recommendation - Exempt security fixes explicitly, and set osvVulnerabilityAlerts to widen the feed past GitHub's advisories for the language ecosystems OSV covers The name matters. Renovate looks for an organization preset at the renovate-config repository, then at this repository under the preset name renovate-config, which resolves to renovate-config.json. It never reads renovate.json here, which is why the onboarding pull request opened this month still proposes the stock recommendation. Neither OSV nor GitHub advisories cover the docker or helm datasources, so an image or chart security fix arrives as an ordinary dashboard entry rather than through the exemption. The preset description says so. No other repository changes behavior when this merges. This one extends the preset and has no dependencies for Renovate to manage, so the change is inert here too. The twelve repositories awaiting onboarding pick the policy up when their onboarding pull requests regenerate, which Renovate does on its own once the preset changes. Related to datum-cloud/infra#4925 Claude-Session: https://claude.ai/code/session_0196U66w5xh9yRsAosKcA3if
ecv
force-pushed
the
claude/quiet-by-default-renovate
branch
from
September 9, 2026 00:20
0271bfe to
ad67db1
Compare
ecv
marked this pull request as ready for review
September 9, 2026 00:23
ecv
enabled auto-merge
September 9, 2026 00:32
ecv
force-pushed
the
claude/quiet-by-default-renovate
branch
from
September 9, 2026 01:02
4bce2a5 to
39babd8
Compare
An audit of the repositories carrying their own config found the same labelling settings copied across auth-ui, email-templates, agents.datum.net, cloud-portal and datum-ui. Several of the audits proposed the same replacement without knowing about each other. Those are organization convention rather than local decisions. Left in place they get copied into every repository that adopts the preset and drift apart afterwards. Key changes: - Label every update the bot opens, using addLabels rather than a packageRule, because top-level labels replace a consumer's own list while addLabels merges with it, and a packageRule matching on package name never matches a lock file maintenance branch - Move the vulnerability labels into the preset's vulnerabilityAlerts block, where they merge with the existing exemption - Exempt lockFileMaintenance from the approval gate The copied configs also carried a priority boost keyed on a security category. Renovate's categories are the fixed manager set, so that rule matched nothing in any of the five repositories and is left out here rather than inherited organization wide. Vulnerability pull requests already open immediately and ignore concurrency limits by default, so nothing is lost. The lockFileMaintenance carve-out closes a change nobody asked for. Repositories that enable it run it unattended on a schedule today, and under a bare gate those runs would have queued on the dashboard waiting for a manual tick. The setting stays off by default, so this changes nothing for a repository that does not enable it. Related to datum-cloud/infra#4925 Claude-Session: https://claude.ai/code/session_0196U66w5xh9yRsAosKcA3if
ecv
force-pushed
the
claude/quiet-by-default-renovate
branch
from
September 9, 2026 01:04
39babd8 to
cccdec9
Compare
mattdjenkinson
approved these changes
Sep 9, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Dependency updates open pull requests across the organization on a bot's schedule. Sixty-one of them request review from a 22 person team, the oldest since August 2025.
This adds that policy, plus the label and security priority settings five repositories had each copied, as a preset under the name Renovate reads when it onboards a repository.
Important
Nothing changes here on merge, because this repository is the preset's only consumer and has no dependencies for Renovate to manage.
Test plan
Related to datum-cloud/infra#4925
https://claude.ai/code/session_0196U66w5xh9yRsAosKcA3if