Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency react-dom to v16.8.6 [SECURITY] #12

Merged
merged 1 commit into from
Apr 7, 2019

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 11, 2019

This PR contains the following updates:

Package Type Update Change References
react-dom devDependencies minor 16.3.2 -> 16.8.6 homepage, source

GitHub Vulnerability Alerts

CVE-2018-6341

React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time. That lack of escaping could lead to a cross-site scripting vulnerability. This vulnerability can only affect some server-rendered React apps. Purely client-rendered apps are not affected.

This issue affected minor releases 16.0.x, 16.1.x, 16.2.x, 16.3.x, and 16.4.x. It was fixed in 16.0.1, 16.1.2, 16.2.1, 16.3.3, and 16.4.2.


Release Notes

facebook/react

v16.8.6

Compare Source

React DOM

v16.8.5

Compare Source

React DOM
React DOM Server
React Shallow Renderer

v16.8.4

Compare Source

React DOM and other renderers
  • Fix a bug where DevTools caused a runtime error when inspecting a component that used a useContext hook. (@​bvaughn in #​14940)

v16.8.3

Compare Source

React DOM
React DOM Server
  • Unwind the context stack when a stream is destroyed without completing, to prevent incorrect values during a subsequent render. (@​overlookmotel in #​14706)
ESLint Plugin for React Hooks

v16.8.2

Compare Source

React DOM
React Test Utils and React Test Renderer

v16.8.1

Compare Source

React DOM and React Test Renderer
React Test Utils

v16.8.0

Compare Source

React
React DOM
React Test Renderer and Test Utils
  • Support Hooks in the shallow renderer. (@​trueadm in #​14567)
  • Fix wrong state in shouldComponentUpdate in the presence of getDerivedStateFromProps for Shallow Renderer. (@​chenesan in #​14613)
  • Add ReactTestRenderer.act() and ReactTestUtils.act() for batching updates so that tests more closely match real behavior. (@​threepointone in #​14744)
ESLint Plugin: React Hooks

v16.7.0

Compare Source

React DOM
Scheduler (Experimental)

v16.6.3

React DOM
React DOM Server

v16.6.2

This release was published in a broken state and should be skipped.

v16.6.1

Compare Source

React DOM
Scheduler (Experimental)

v16.6.0

Compare Source

React
React DOM
React DOM Server
Scheduler (Experimental)

v16.5.2

Compare Source

React DOM
Schedule (Experimental)

v16.5.1

Compare Source

React
React DOM
Schedule (Experimental)

v16.5.0

Compare Source

React
React DOM
React DOM Server
React Test Renderer and Test Utils
React ART
Schedule (Experimental)
  • New package for cooperatively scheduling work in a browser environment. It's used by React internally, but its public API is not finalized yet. (@​flarnie in #​12624)

v16.4.2

Compare Source

React DOM Server

v16.4.1

Compare Source

React
  • You can now assign propTypes to components returned by React.ForwardRef. (@​bvaughn in #​12911)
React DOM
React DOM Server
React Test Renderer
  • Allow multiple root children in test renderer traversal API. (@​gaearon in #​13017)
  • Fix getDerivedStateFromProps() in the shallow renderer to not discard the pending state. (@​fatfisz in #​13030)

v16.4.0

React
React DOM
React Test Renderer
  • Fix the getDerivedStateFromProps() support to match the new React DOM behavior. (@​koba04 in #​12676)
  • Fix a testInstance.parent crash when the parent is a fragment or another special node. (@​gaearon in #​12813)
  • forwardRef() components are now discoverable by the test renderer traversal methods. (@​gaearon in #​12725)
  • Shallow renderer now ignores setState() updaters that return null or undefined. (@​koba04 in #​12756)
React ART
React Call Return (Experimental)
  • This experiment was deleted because it was affecting the bundle size and the API wasn't good enough. It's likely to come back in the future in some other form. (@​gaearon in #​12820)
React Reconciler (Experimental)

v16.3.3

React DOM Server

Renovate configuration

📅 Schedule: "" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot. View repository job log here.

@coveralls
Copy link

coveralls commented Mar 11, 2019

Pull Request Test Coverage Report for Build 75

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 59: 0.0%
Covered Lines: 321
Relevant Lines: 321

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/npm-react-dom-vulnerability branch from 649f425 to 21f2bf4 Compare March 22, 2019 16:55
@renovate renovate bot changed the title Update dependency react-dom to v16.8.4 [SECURITY] Update dependency react-dom to v16.8.5 [SECURITY] Mar 22, 2019
@renovate renovate bot force-pushed the renovate/npm-react-dom-vulnerability branch 4 times, most recently from 89eae0d to a4f039e Compare March 24, 2019 05:49
@renovate renovate bot force-pushed the renovate/npm-react-dom-vulnerability branch from a4f039e to f72f01c Compare March 28, 2019 09:53
@renovate renovate bot changed the title Update dependency react-dom to v16.8.5 [SECURITY] Update dependency react-dom to v16.8.6 [SECURITY] Mar 28, 2019
@10xjs 10xjs merged commit c0b1cd3 into master Apr 7, 2019
@10xjs 10xjs deleted the renovate/npm-react-dom-vulnerability branch April 7, 2019 20:56
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.

None yet

3 participants