Skip to content

chore: disable Renovate vulnerabilityAlerts so security flows into normal updates #1834

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Aureliolo merged 1 commit into from
May 9, 2026
Merged

chore: disable Renovate vulnerabilityAlerts so security flows into normal updates #1834

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,7 @@
"prHourlyLimit": 5,
"separateMajorMinor": false,
"vulnerabilityAlerts": {
"enabled": true,
"schedule": ["at any time"],
"labels": ["dependencies", "security"]
"enabled": false
},
Comment on lines +25 to 26
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Disabling vulnerabilityAlerts entirely removes the security label and specific metadata (such as CVE links and severity levels) from your pull requests. This makes security fixes indistinguishable from routine dependency updates within your grouped PRs, which may lead to them being overlooked during review or treated with lower priority.

To achieve your goal of 'folding' security updates into the weekly groups while maintaining visibility and security metadata, you can keep the feature enabled but align its schedule with your global one. This ensures that security fixes are still identified as such but are only processed during your Saturday window. The existing packageRules (which match by manager) will then group these updates into your 'Python', 'Web', and 'Infrastructure' batches as intended.

    "enabled": true,
    "schedule": ["* 0-6 * * 6"],
    "labels": ["dependencies", "security"]
  },

"packageRules": [
{
Expand Down
Loading