Context
Split off from #2355 (Harden Renovate config). The root renovate.json currently lacks a vulnerabilityAlerts block, which means GitHub/OSV security advisories flow through the same schedules as routine dependency updates.
Gap
Renovate's vulnerabilityAlerts configuration opts into security advisories with their own schedule, labels, and merge policy, separate from the main dependency update flow. Without it, security-flagged updates wait for the same Sunday/daily schedule windows as routine bumps.
Proposal
Add a top-level block to renovate.json:
"vulnerabilityAlerts": {
"enabled": true,
"labels": ["Dependencies", "Security"],
"automerge": false,
"dependencyDashboardApproval": false,
"schedule": ["at any time"]
}
Design decisions
automerge: false - Drupal SA-CORE advisories occasionally ship in minor releases that bring API changes. Downstream projects inheriting Vortex should not silently merge security updates without review.
schedule: ["at any time"] - security fixes bypass the Sunday/daily schedule windows used by the main rules.
- Labels
["Dependencies", "Security"] - reuses the existing Dependencies label plus a new Security label for filtering.
dependencyDashboardApproval: false - vulnerability PRs are created immediately without waiting for explicit approval on the dashboard.
Acceptance criteria
References
Context
Split off from #2355 (Harden Renovate config). The root
renovate.jsoncurrently lacks avulnerabilityAlertsblock, which means GitHub/OSV security advisories flow through the same schedules as routine dependency updates.Gap
Renovate's
vulnerabilityAlertsconfiguration opts into security advisories with their own schedule, labels, and merge policy, separate from the main dependency update flow. Without it, security-flagged updates wait for the same Sunday/daily schedule windows as routine bumps.Proposal
Add a top-level block to
renovate.json:Design decisions
automerge: false- Drupal SA-CORE advisories occasionally ship in minor releases that bring API changes. Downstream projects inheriting Vortex should not silently merge security updates without review.schedule: ["at any time"]- security fixes bypass the Sunday/daily schedule windows used by the main rules.["Dependencies", "Security"]- reuses the existingDependencieslabel plus a newSecuritylabel for filtering.dependencyDashboardApproval: false- vulnerability PRs are created immediately without waiting for explicit approval on the dashboard.Acceptance criteria
renovate.jsoncontains the block above..vortex/installer/tests/Fixtures/handler_process/regenerated viaahoy update-snapshots.Securitylabel needs to be created in the template repository.References