Open greenkeeper[bot] opened 4 years ago
After pinning to 16.10.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
react was updated from 16.11.0
to 16.12.0
.devDependency
react-dom was updated from 16.11.0
to 16.12.0
.devDependency
react-test-renderer was updated from 16.11.0
to 16.12.0
.Your tests are still failing with these versions. Compare changes
devDependency
react was updated from 16.12.0
to 16.13.0
.devDependency
react-dom was updated from 16.12.0
to 16.13.0
.devDependency
react-test-renderer was updated from 16.12.0
to 16.13.0
.Your tests are still failing with these versions. Compare changes
React.createFactory()
(@trueadm in #17878)style
may cause an unexpected collision (@sophiebits in #14181, #18002)unstable_createPortal
(@trueadm in #17880)onMouseEnter
being fired on disabled buttons (@AlfredoGJ in #17675)shouldComponentUpdate
twice when developing in StrictMode
(@bvaughn in #17942)version
property to ReactDOM (@ealush in #15780)toString()
of dangerouslySetInnerHTML
(@sebmarkbage in #17773)ReactDOM.createRoot()
(@trueadm in #17937)ReactDOM.createRoot()
callback params and added warnings on usage (@bvaughn in #17916)SuspenseList
CPU bound heuristic (@sebmarkbage in #17455)isPending
only being true when transitioning from inside an input event (@acdlite in #17382)React.memo
components dropping updates when interrupted by a higher priority update (@acdlite in #18091)
There have been updates to the react monorepo:
devDependency
react was updated from16.10.2
to16.11.0
.devDependency
react-dom was updated from16.10.2
to16.11.0
.devDependency
react-test-renderer was updated from16.10.2
to16.11.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
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/goto-bus-stop/bulmare/builds/601593336?utm_source=github_status&utm_medium=notification)).Release Notes for 16.11.0 (October 22, 2019)
React DOM
mouseenter
handlers from firing twice inside nested React containers. @yuanoook in #16928unstable_createRoot
andunstable_createSyncRoot
experimental APIs. (These are available in the Experimental channel ascreateRoot
andcreateSyncRoot
.) (@acdlite in #17088)Artifacts
• react: https://unpkg.com/react@16.11.0/umd/
• react-art: https://unpkg.com/react-art@16.11.0/umd/
• react-dom: https://unpkg.com/react-dom@16.11.0/umd/
• react-is: https://unpkg.com/react-is@16.11.0/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.11.0/umd/
• scheduler: https://unpkg.com/scheduler@0.17.0/umd/
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: