Skip to content

Switch dependency updates from Dependabot to Renovate - #492

Draft
chalin wants to merge 4 commits into
google:mainfrom
chalin:chalin-m24-renovate-config-2026-0826
Draft

Switch dependency updates from Dependabot to Renovate#492
chalin wants to merge 4 commits into
google:mainfrom
chalin:chalin-m24-renovate-config-2026-0826

Conversation

@chalin

@chalin chalin commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator
  • Supersedes Configure Renovate #485 (the Renovate onboarding proposal): commits a curated renovate.json5 instead of config:recommended, aligned with the docsy repo's config: 7-day minimumReleaseAge, Monday-only schedule, npm + github-actions managers only (gomod and docker pins stay manual, per CONTRIBUTING.md).
  • Ports dependabot.yml's carve-outs as package rules (hugo-extended's manual two-step flow; theme-managed bootstrap and Font Awesome), then retires the file: running both bots doubles the PR noise, and repo-level Dependabot security updates don't depend on it.
  • Draws the security line: Dependabot security updates own vulnerability PRs; Renovate's vulnerabilityAlerts is off (immediate, age-exempt duplicates otherwise). Also off, with reasons in-file: lockFileMaintenance and configMigration (both pulled in by config:best-practices).
  • Merge order: close Configure Renovate #485 first (unmerged; its renovate.json would shadow this file in config-search order), then merge; a committed config onboards the repo regardless of the closed onboarding PR.
  • Validation: renovate-config-validator --strict (44.35.2) passes; site tests and check:links pass. Post-merge: verify the Dependency Dashboard, and that an admin confirms repo-level Dependabot security updates are enabled (API check needs admin read).

chalin added 4 commits August 26, 2026 20:44
Commits the renovate.json5 that supersedes Renovate's onboarding
proposal (google#485), aligned with the docsy repo's config: 7-day
minimumReleaseAge, npm + github-actions managers only, hugo-extended
and theme-managed assets excluded (same carve-outs dependabot.yml
held). Repo-level security alerts are unaffected: grouped security
PRs never depended on dependabot.yml.

Config validated with renovate-config-validator --strict (44.35.2).
- disable lockFileMaintenance (via config:best-practices): a weekly full
  lock re-resolve pulls in-range latests UNGATED by minimumReleaseAge
- hugo-extended comment: enabled:false silences Renovate security bumps
  too; name the actual net (repo-level Dependabot security updates +
  fail-closed installs), not 'alerts'
- age-exemptions comment: drop the claims about PR-time review that
  internalChecksFilter:strict invalidates
- vulnerabilityAlerts off: Dependabot security updates own vuln PRs;
  Renovate's are immediate, unscheduled, age-exempt duplicates
- configMigration off: migration PRs may rewrite JSON5 to JSON and drop
  the comments this file keeps its policy in
- schedule widens to all Monday: a narrow window can miss the hosted
  scheduler's daily visit on a not-yet-activated repo, never bootstrapping
- lockFileMaintenance comment: correct rationale (lock churn + the
  ETARGET age-gate fallback; v44 gates the normal path with --before)
- bootstrap/FA rule comment: names the Dependabot-security-PR behavior
  the retired unscoped ignore used to suppress
- age-exemptions comment: pending-on-dashboard, not PR-time review
Colon/semicolon constructs replace the spaced-dash asides; drop the
stale claim that security updates bypass the age gate (Renovate raises
no security PRs here since vulnerabilityAlerts went off).
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.

1 participant