An in-range update of react is breaking the build 🚨

[greenkeeper]

There have been updates to the react monorepo:

• • The devDependency react was updated from 16.12.0 to 16.13.0.

• The devDependency react-dom was updated from 16.12.0 to 16.13.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ Format files: null
• ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
• ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.

---

Release Notes for 16.13.0 (February 26, 2020)

React

• Warn when a string ref is used in a manner that's not amenable to a future codemod (@lunaruan in #17864)
• Deprecate React.createFactory() (@trueadm in #17878)

React DOM

• Warn when changes in style may cause an unexpected collision (@sophiebits in #14181, #18002)
• Warn when a function component is updated during another component's render phase (@acdlite in #17099)
• Deprecate unstable_createPortal (@trueadm in #17880)
• Fix onMouseEnter being fired on disabled buttons (@AlfredoGJ in #17675)
• Call shouldComponentUpdate twice when developing in StrictMode (@bvaughn in #17942)
• Add version property to ReactDOM (@ealush in #15780)
• Don't call toString() of dangerouslySetInnerHTML (@sebmarkbage in #17773)
• Show component stacks in more warnings (@gaearon in #17922, #17586)

Concurrent Mode (Experimental)

• Warn for problematic usages of ReactDOM.createRoot() (@trueadm in #17937)
• Remove ReactDOM.createRoot() callback params and added warnings on usage (@bvaughn in #17916)
• Don't group Idle/Offscreen work with other work (@sebmarkbage in #17456)
• Adjust SuspenseList CPU bound heuristic (@sebmarkbage in #17455)
• Add missing event plugin priorities (@trueadm in #17914)
• Fix isPending only being true when transitioning from inside an input event (@acdlite in #17382)
• Fix React.memo components dropping updates when interrupted by a higher priority update (@acdlite in #18091)
• Don't warn when suspending at the wrong priority (@gaearon in #17971)
• Fix a bug with rebasing updates (@acdlite and @sebmarkbage in #17560, #17510, #17483, #17480)

Artifacts

• react: https://unpkg.com/react@16.13.0/umd/
• react-art: https://unpkg.com/react-art@16.13.0/umd/
• react-dom: https://unpkg.com/react-dom@16.13.0/umd/
• react-is: https://unpkg.com/react-is@16.13.0/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.13.0/umd/
• scheduler: https://unpkg.com/scheduler@0.19.0/umd/

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 16.12.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency react was updated from 16.13.0 to 16.13.1.
• The devDependency react-dom was updated from 16.13.0 to 16.13.1.

Your tests are still failing with these versions. Compare changes