Reduce usage of the trim dependency #130863
Merged
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
We forcefully upgrade the trim sub-dependency to v1.0.1 because of an old know security vulnerability. Two of our dependencies who previously depended on trim no longer does so, and we can therefore now upgrade those to get rid of the warnings generated because of this forceful upgrade.
watson
added
release_note:skip
|
The only dependency still depending on an old version of |
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @watson |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
watson
pushed a commit
that referenced
this pull request
Apr 25, 2022
We forcefully upgrade the trim sub-dependency to v1.0.1 because of an old known security vulnerability. Two of our dependencies who previously depended on trim no longer does so, and we can therefore now upgrade those to get rid of the warnings generated because of this forceful upgrade. (cherry picked from commit 641fc10) # Conflicts: # yarn.lock
dmlemeshko
pushed a commit
to dmlemeshko/kibana
that referenced
this pull request
May 5, 2022
We forcefully upgrade the trim sub-dependency to v1.0.1 because of an old known security vulnerability. Two of our dependencies who previously depended on trim no longer does so, and we can therefore now upgrade those to get rid of the warnings generated because of this forceful upgrade.
kertal
pushed a commit
to kertal/kibana
that referenced
this pull request
May 24, 2022
We forcefully upgrade the trim sub-dependency to v1.0.1 because of an old known security vulnerability. Two of our dependencies who previously depended on trim no longer does so, and we can therefore now upgrade those to get rid of the warnings generated because of this forceful upgrade.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We forcefully upgrade the trim sub-dependency to v1.0.1 because of an old known security vulnerability. Two of our dependencies who previously depended on trim no longer does so, and we can therefore now upgrade those to get rid of the warnings generated because of this forceful upgrade.