Skip to content

chore(renovate): enable vulnerabilityAlerts so CVE bumps fire off-schedule - #5

Merged
bikramnehra merged 1 commit into
mainfrom
chore/renovate-vulnerability-alerts
Aug 4, 2026
Merged

chore(renovate): enable vulnerabilityAlerts so CVE bumps fire off-schedule#5
bikramnehra merged 1 commit into
mainfrom
chore/renovate-vulnerability-alerts

Conversation

@bikramnehra

Copy link
Copy Markdown
Contributor

Motivation

Renovate's weekly Monday cadence is right for normal dep bumps but wrong for security-flagged ones — a P0 CVE landing Tuesday would sit up to seven days until the next scan. Today's Inspector-driven push surfaced 35 critical findings on forge-prod nodes that had accumulated since the July 20 Renovate outage; keeping the response time short is worth a small config lever.

Change

Enable vulnerabilityAlerts at the shared preset. Renovate reads GitHub's Dependabot alert feed for each repo and, on a hit, opens a PR immediately — bypassing the cron. Normal bumps keep batching on Monday; security-flagged ones jump the queue.

Requirements

Dependabot Security Alerts must be enabled at the org/repo level (Settings → Code security). This has been standing policy since we replaced Dependabot with Renovate, so no additional org-side change is needed.

Effect

  • Any repo extending this preset (currently forge and forge-infra) picks up the behavior on the next Renovate run.
  • Resulting PRs are labeled security for easy review-queue filtering.
  • The manual "trigger Renovate to run again" checkbox on the Dependency Dashboard remains as the escape hatch for anything else urgent.

Followup (not blocking)

renovate-config-validator warns that the file is JSON5-syntax inside a .json extension: Support for this will be removed in a future release. Renovate accepts it today. Two options for later:

  1. Rename back to default.json5 AND update both consumers to github>HyperbolicLabs/.github//default.json5 (explicit path)
  2. Convert the preset to strict JSON, moving the comment explanations to a companion README in this repo

Both keep the current behavior; option 1 preserves the inline WHY comments better. Filing a followup issue separately.

Renovate's weekly Monday cadence is right for normal dep bumps but wrong
for security-flagged ones — a P0 CVE landing Tuesday would sit up to
seven days until the next scan. `vulnerabilityAlerts.enabled` tells
Renovate to read GitHub's Dependabot alert feed and open PRs
immediately on a hit, bypassing the cron. Normal bumps keep batching
on Monday; only the security-tagged ones jump the queue.

Depends on Dependabot Security Alerts being enabled at the org/repo
level (Settings → Code security), which was already standing policy
before Renovate took over dep bumps.

Labels the resulting PRs `security` so they're easy to filter in the
review queue.
@bikramnehra
bikramnehra merged commit 66d41c1 into main Aug 4, 2026
1 check failed
@bikramnehra
bikramnehra deleted the chore/renovate-vulnerability-alerts branch August 4, 2026 23:39
bikramnehra added a commit that referenced this pull request Aug 4, 2026
The rename PR (#4) moved default.json5 → default.json but missed the
CI workflow, which is hardcoded to the old filename. Every run since
has failed with `File does not exist "default.json5"` — PR #4 and PR #5
both merged past a red check because the check isn't required.

Point the validator at default.json. Confirmed locally: exit 0, "Config
validated successfully" (with the harmless JSON5-in-.json deprecation
warn, which does not fail --strict).
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