Repository navigation
fix(sc4): scope npm lock resolution to owning projects #940
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
chrisknvidia
wants to merge
4
commits into
NVIDIA:main
Choose a base branch
from
chrisknvidia:feat/christopherk/npm-project-lock-scope
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1f40ac2
fix(supply-chain): scope npm lock resolution to owning projects
chrisknvidia 8326590
fix(supply-chain): keep alias target versions out of slot inference
chrisknvidia e2f5410
fix(supply-chain): preserve legacy npm workspace lock resolution
chrisknvidia 26d3b7e
fix(supply-chain): preserve scoped lock parse and filename contracts
chrisknvidia File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we prevent this skipped alias slot from falling back to an ancestor's package? For example, let the root install
lodash@4.17.20and workspacepackages/adeclarelodash: npm:node-forge@1.4.2, with that alias recorded atpackages/a/node_modules/lodash. Thiscontinuedrops the nearer slot, so the laterChainMapreturns the root'slodashversion._apply_locked_versionsthen attributes a resolvedlodash==4.17.20vulnerability to the workspace manifest, although its dependency is node-forge. Please preserve the alias as a lookup boundary, or keep alias specs from accepting unrelated registry pins, and cover this workspace-shadowing case. The existing alias test has no ancestor pin and misses it.