feat: Test vulnerability alert ordering with explicit config - #417
Closed
jsonbailey wants to merge 2 commits into
Closed
feat: Test vulnerability alert ordering with explicit config#417jsonbailey wants to merge 2 commits into
jsonbailey wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Testing whether defining vulnerabilityAlerts after the preset's enabled:false packageRule causes security updates to be created.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
vulnerabilityAlertsandosvVulnerabilityAlertsconfig at the repo level, after the preset'senabled: falsepackageRuleContext
The
sdk-rubypreset setsenabled: falsefor all bundler packages to suppress routine dependency PRs. However, Renovate's vulnerability alert system should bypassenabled: falsevia aforcemechanism. The log from js-core showed that npm packages with known CVEs were logged as "is disabled" rather than generating PRs.This PR tests whether explicitly re-declaring
vulnerabilityAlerts.enabled: trueat the repo level (after the preset extends) changes the behavior.