Upgrade to undici 6.27.0 to resolve transitive CVEs - fixes #1517 - #1518
Merged
Conversation
Member
|
thanks, agree! |
Member
|
hrm, we spent some time thinking about the version - unlocking this becomes a server major because it drops a lot of node versions |
Contributor
Author
|
Upgrading to |
Contributor
|
This has no effect, until release is made: so #1517 shouldn't be closed yet |
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
4 participants
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.
Unpinning undici so that further fixes to undici@6.x will be fixable in consumers, through their lockfiles