feat(npm): optimize remediation to detect already updated branches #14084
Conversation
This file contains 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 PR is included in version 31.69.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
viceice
reviewed
Feb 8, 2022
| } else { | ||
| logger.debug( | ||
| { anyVersionLocked }, | ||
| `Found alternative versions of qs` |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes:
Enhances transitive remediation logic to detect when a dependency is already updated via either:
This should remove some unnecessary retrying of updates each run.
Context:
Performance
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: