chore(renovate): enable gomod + OSV vuln alerts; automerge patches (not aztec)#653
Open
bussyjd wants to merge 1 commit into
Open
chore(renovate): enable gomod + OSV vuln alerts; automerge patches (not aztec)#653bussyjd wants to merge 1 commit into
bussyjd wants to merge 1 commit into
Conversation
…ot aztec) Three Renovate flow fixes surfaced while auditing why image pins drift: - Enable the `gomod` manager. It was excluded by `enabledManagers`, so all ~121 direct Go dependencies got zero updates — the likely source of the open Dependabot vulnerabilities on the default branch. - Turn on vulnerability-driven PRs via `osvVulnerabilityAlerts` (OSV database, works without the GitHub Dependabot-alerts permission the dashboard reports as missing) plus an explicit `vulnerabilityAlerts` block with security labels. - Auto-merge `patch`-level updates once required checks pass (`automerge` + `platformAutomerge`), so low-risk bumps stop piling up as unmerged PRs. Aztec is explicitly excluded (fast-moving testnet — nightly tags / frequent majors), always reviewed. No change to the existing custom managers or the major-update approval gates (frontend / hermes / remote-signer stay dashboard-gated).
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
1 participant
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.
Why
Auditing why image pins drift (reth was a minor behind) showed Renovate is
working — it opens grouped PRs (#604 clients, #642 cloudflared, #603 tools,
#575/#576 aztec) — but two gaps let updates rot and security bumps slip:
gomodwas never enabled.enabledManagerslisted onlycustom.regex+github-actions, so ~121 direct Go deps got no Renovate updates. This isalmost certainly the source of the open Dependabot vulnerabilities on
main.automerge. Every update waited on a manual merge, so low-risk bumpspiled up for weeks.
What
gomodinenabledManagers.osvVulnerabilityAlerts: true(OSV database — workswithout the GitHub Dependabot-alerts permission the dependency dashboard
reports as missing) + an explicit
vulnerabilityAlertsblock withsecuritylabels.
patchupdates once required checks pass (automerge+platformAutomerge), with Aztec explicitly excluded (fast-moving testnet —nightly tags / frequent majors; always reviewed).
Existing custom managers and the major-update approval gates (frontend / hermes /
remote-signer remain dashboard-gated) are unchanged.
Follow-ups (not in this PR — repo settings / org)
it can't access them) to also get GitHub-native vuln alerts alongside OSV.
aquasecurity/trivy-actionlookup failure in the 3docker-publish-*workflows (dashboard Dependency Dashboard #545).
from merging (e.g. chore(deps): update ethereum el/cl client updates #604) — worth reviewing so
automergecan actually land.Validation
renovate.jsonis valid JSON; all keys are standard Renovate schema.