fix(arborist): keep locked versions when extension rules change - #9989
Open
manzoorwanijk wants to merge 1 commit into
Open
manzoorwanijk wants to merge 1 commit into
manzoorwanijk wants to merge 1 commit into
Conversation
manzoorwanijk
marked this pull request as ready for review
September 15, 2026 11:03
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.
When the
packageExtensionsor.npm-extensionhash changes,npm installupgraded every affected package to the newest version in range, even though only its manifest needed refreshing.The affected nodes are detached and rebuilt from the edge spec, so pacote picked the newest match instead of the locked version.
#detachForExtensionRefreshnow remembers the locked registry versions in each detached subtree, and#nodeFromSpecrefetches the newest one that still satisfies the edge.Linked, bundled and audit-vulnerable nodes are not reused,
npm update <name>and explicit installs still upgrade, and a locked version that is no longer published (ETARGET) falls back to the edge spec.References
Fixes #9981