Skip to content

Remove unnecessary yarn resolutions - #4195

Draft
Elizabeth Craig (ecraig12345) wants to merge 1 commit into
mainfrom
user/elcraig/fix-pinning
Draft

Remove unnecessary yarn resolutions#4195
Elizabeth Craig (ecraig12345) wants to merge 1 commit into
mainfrom
user/elcraig/fix-pinning

Conversation

@ecraig12345

@ecraig12345 Elizabeth Craig (ecraig12345) commented Aug 17, 2026

Copy link
Copy Markdown
Member

Description of changes

Update yarn resolutions to remove resolutions that are unnecessary (either the bad version is no longer referenced, or the fixed version is in-range), and scope down the remaining resolutions where possible.

Recommended procedure for security updates in nested dependencies

In general, to handle security updates in nested dependencies, look at yarn.lock and/or use yarn why to determine which of the following cases apply:

  • Range is ^ or ~ and fixed version is in range: delete lock file entry, reinstall
  • Something pins the dep to a specific version (same major or 0.x-minor as fixed version): set resolution to "foo@npm:1.2.3": "^1.2.3" and reinstall
  • Fixed version of nested dependency is different major or 0.x-minor from fix:
    • find what depends on it and try to update that
      • direct dep of repo: try updating directly
      • nested dep: same method of deleting from lock file, maybe up to multiple parents
    • for dev or unpublished tool deps only, check the changelog for the new version to see if it's compatible, and if so use a targeted resolution as above

Verification

PR build passes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant