fix: don't apply min-release-age in npm audit signatures#9430
Merged
owlstronaut merged 1 commit intoMay 28, 2026
Conversation
…installed signatures
2 tasks
JamieMagee
changed the title
npm audit signatures
owlstronaut
approved these changes
May 28, 2026
Contributor
|
🎉 Backport to |
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.
audit signatureschecks the exact versions already installed, butmin-release-age/beforewas being passed into the manifest lookup and failing with ETARGET on versionsnpm cihad just installed. Settingbefore: nullfor that lookup fixes it. Fixes #9277.