Skip to content

chore(renovate): enable gomod + OSV vuln alerts; automerge patches (not aztec)#653

Open
bussyjd wants to merge 1 commit into
mainfrom
chore/renovate-gomod-vuln-automerge
Open

chore(renovate): enable gomod + OSV vuln alerts; automerge patches (not aztec)#653
bussyjd wants to merge 1 commit into
mainfrom
chore/renovate-gomod-vuln-automerge

Conversation

@bussyjd

@bussyjd bussyjd commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

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:

  1. gomod was never enabled. enabledManagers listed only custom.regex +
    github-actions, so ~121 direct Go deps got no Renovate updates. This is
    almost certainly the source of the open Dependabot vulnerabilities on main.
  2. No automerge. Every update waited on a manual merge, so low-risk bumps
    piled up for weeks.

What

  • Enable gomod in enabledManagers.
  • Vulnerability-driven PRs: osvVulnerabilityAlerts: true (OSV database — works
    without the GitHub Dependabot-alerts permission the dependency dashboard
    reports as missing) + an explicit vulnerabilityAlerts block with security
    labels.
  • Auto-merge patch updates 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)

Validation

renovate.json is valid JSON; all keys are standard Renovate schema.

…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).
@OisinKyne OisinKyne force-pushed the chore/renovate-gomod-vuln-automerge branch from 56e5441 to aa5c6ed Compare June 18, 2026 15:14
@OisinKyne

Copy link
Copy Markdown
Contributor

I don't support any kind of auto-merge to main considering the supply chain attacks going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants