fix(arborist): honor min-release-age-exclude when reify re-resolves#9720
Draft
gopalsunkari860 wants to merge 1 commit into
Draft
fix(arborist): honor min-release-age-exclude when reify re-resolves#9720gopalsunkari860 wants to merge 1 commit into
gopalsunkari860 wants to merge 1 commit into
Conversation
… node missing resolved
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
reify.js re-resolves nodes with no resolved field (which omit-lockfile-registry-resolved produces) via a bare
name@version spec, passing the raw unfiltered before cutoff to pacote — unlike build-ideal-tree.js, it never checks
min-release-age-exclude, so excluded packages still got rejected with ETARGET during npm ci/reify
Fix for the issue of 9715