Closed greenkeeper[bot] closed 4 years ago
After pinning to 16.8.6 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.9.0
to 16.10.0
.devDependency
react-dom was updated from 16.9.0
to 16.10.0
.devDependency
react-test-renderer was updated from 16.9.0
to 16.10.0
.Your tests are still failing with these versions. Compare changes
devDependency
react was updated from 16.10.0
to 16.10.1
.devDependency
react-dom was updated from 16.10.0
to 16.10.1
.devDependency
react-test-renderer was updated from 16.10.0
to 16.10.1
.Your tests are still failing with these versions. Compare changes
devDependency
react was updated from 16.10.1
to 16.10.2
.devDependency
react-dom was updated from 16.10.1
to 16.10.2
.devDependency
react-test-renderer was updated from 16.10.1
to 16.10.2
.Your tests are still failing with these versions. Compare changes
β’ react: https://unpkg.com/react@16.10.2/umd/
β’ react-art: https://unpkg.com/react-art@16.10.2/umd/
β’ react-dom: https://unpkg.com/react-dom@16.10.2/umd/
β’ react-is: https://unpkg.com/react-is@16.10.2/umd/
β’ react-test-renderer: https://unpkg.com/react-test-renderer@16.10.2/umd/
β’ scheduler: https://unpkg.com/scheduler@0.16.2/umd/
devDependency
react was updated from 16.10.2
to 16.11.0
.devDependency
react-dom was updated from 16.10.2
to 16.11.0
.devDependency
react-test-renderer was updated from 16.10.2
to 16.11.0
.Your tests are still failing with these versions. Compare changes
mouseenter
handlers from firing twice inside nested React containers. @yuanoook in #16928unstable_createRoot
and unstable_createSyncRoot
experimental APIs. (These are available in the Experimental channel as createRoot
and createSyncRoot
.) (@acdlite in #17088)β’ 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/
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
There have been updates to the react monorepo:
devDependency
react was updated from16.8.6
to16.9.0
.devDependency
react-dom was updated from16.8.6
to16.9.0
.devDependency
react-test-renderer was updated from16.8.6
to16.9.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/react-abstract-autocomplete/builds/569759482?utm_source=github_status&utm_medium=notification)).Release Notes for 16.9.0 (August 8, 2019)
React
<React.Profiler>
API for gathering performance measurements programmatically. (@bvaughn in #15172)unstable_ConcurrentMode
in favor ofunstable_createRoot
. (@acdlite in #15532)React DOM
UNSAFE_*
lifecycle methods. (@bvaughn in #15186 and @threepointone in #16103)javascript:
URLs as a common attack surface. (@sebmarkbage in #15047)disablePictureInPicture
attribute on<video>
. (@eek in #15334)onLoad
event for<embed>
. (@cherniavskii in #15614)useState
state from DevTools. (@bvaughn in #14906)setState
is called fromuseEffect
, creating a loop. (@gaearon in #15180)findDOMNode
for components wrapped in<Suspense>
. (@acdlite in #15312)!important
style. (@acdlite in #15861 and #15882)React DOM Server
React Test Utilities and Test Renderer
act(async () => ...)
for testing asynchronous state updates. (@threepointone in #14853)act
from different renderers. (@threepointone in #16039 and #16042)act()
call. (@threepointone in #15763 and #16041)act
from the wrong renderer. (@threepointone in #15756)Artifacts
β’ react: https://unpkg.com/react@16.9.0/umd/
β’ react-art: https://unpkg.com/react-art@16.9.0/umd/
β’ react-dom: https://unpkg.com/react-dom@16.9.0/umd/
β’ react-is: https://unpkg.com/react-is@16.9.0/umd/
β’ react-test-renderer: https://unpkg.com/react-test-renderer@16.9.0/umd/
β’ scheduler: https://unpkg.com/scheduler@0.15.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: