This repository was archived by the owner on Oct 11, 2022. It is now read-only.
🚨 [security] Upgrade react-dom: 16.2.0 → 16.2.1 (patch)#167
Open
depfu[bot] wants to merge 1 commit intomasterfrom
Open
🚨 [security] Upgrade react-dom: 16.2.0 → 16.2.1 (patch)#167depfu[bot] wants to merge 1 commit intomasterfrom
depfu[bot] wants to merge 1 commit intomasterfrom
Conversation
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 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.
🚨 Your version of react-dom has known security vulnerabilities 🚨
Advisory: CVE-2018-6341
Disclosed: January 04, 2019
URL: https://nvd.nist.gov/vuln/detail/CVE-2018-6341
Low severity vulnerability that affects react-dom
🚨 We recommend to merge and deploy this update as soon as possible! 🚨
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ react-dom (16.2.0 → 16.2.1) · Repo · Changelog
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands