Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
mizdra
changed the title
Member
Author
|
Thank you! |
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
2 participants
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
minimumReleaseAgefrom npm-only to all datasourcesminimumReleaseAge.jsonand inlined the setting directly intodefault.jsonBackground
Supply chain attacks have been increasing beyond npm, making it desirable to apply
minimumReleaseAgeto all datasources. The separate preset existed to allow disabling it viaignorePresets, but disabling this security-critical option is rarely needed and should be avoided as much as possible. We removed the preset to encourage users to keep it enabled.Test Plan
I won’t run any tests. Since this is a trivial change, let’s merge it and see how it goes.
🤖 Generated with Claude Code