Open greenkeeper[bot] opened 6 years ago
After pinning to 16.5.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.6.0
to 16.6.1
.devDependency
react-dom was updated from 16.6.0
to 16.6.1
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.6.1
to 16.6.2
.devDependency
react-dom was updated from 16.6.1
to 16.6.2
.Your tests are still failing with these versions. Compare changes
devDependency
react was updated from 16.6.2
to 16.6.3
.devDependency
react-dom was updated from 16.6.2
to 16.6.3
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.6.3
to 16.7.0
.devDependency
react-dom was updated from 16.6.3
to 16.7.0
.Your tests are passing again with this update. Explicitly upgrade to these versions π
React.lazy
for large numbers of lazily-loaded components. (@acdlite in #14429)react-dom/server@16.6
and react@<16.6
. (@gaearon in #14291)devDependency
react was updated from 16.7.0
to 16.8.0
.devDependency
react-dom was updated from 16.7.0
to 16.8.0
.Your tests are still failing with these versions. Compare changes
devDependency
react was updated from 16.8.0
to 16.8.1
.devDependency
react-dom was updated from 16.8.0
to 16.8.1
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.8.1
to 16.8.2
.devDependency
react-dom was updated from 16.8.1
to 16.8.2
.Your tests are passing again with this update. Explicitly upgrade to these versions π
ReactDOM.render
being ignored inside useEffect
. (@gaearon in #14799)useImperativeHandle
to work correctly when no deps are specified. (@gaearon in #14801)crossOrigin
attribute to work in SVG image
elements. (@aweary in #14832)act()
warning. (@threepointone in #14855)devDependency
react was updated from 16.8.2
to 16.8.3
.devDependency
react-dom was updated from 16.8.2
to 16.8.3
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.8.2
to 16.8.3
.devDependency
react-dom was updated from 16.8.2
to 16.8.3
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.8.3
to 16.8.4
.devDependency
react-dom was updated from 16.8.3
to 16.8.4
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.8.4
to 16.8.5
.devDependency
react-dom was updated from 16.8.4
to 16.8.5
.Your tests are passing again with this update. Explicitly upgrade to these versions π
size
attribute. (@kulek1 in #14242)useEffect(async () => ...)
warning message. (@gaearon in #15118)setState
in shallow renderer to work with Hooks. (@gaearon in #15120)React.memo
. (@aweary in #14816)forwardRef
. (@eps1lon in #15100)devDependency
react was updated from 16.8.4
to 16.8.5
.devDependency
react-dom was updated from 16.8.4
to 16.8.5
.Your tests are passing again with this update. Explicitly upgrade to these versions π
size
attribute. (@kulek1 in #14242)useEffect(async () => ...)
warning message. (@gaearon in #15118)setState
in shallow renderer to work with Hooks. (@gaearon in #15120)React.memo
. (@aweary in #14816)forwardRef
. (@eps1lon in #15100)devDependency
react was updated from 16.8.5
to 16.8.6
.devDependency
react-dom was updated from 16.8.5
to 16.8.6
.Your tests are passing again with this update. Explicitly upgrade to these versions π
useReducer()
. (@acdlite in #15124)contextType
is set to Context.Consumer
instead of Context
. (@aweary in #14831)contextType
is set to invalid values. (@gaearon in #15142)devDependency
react was updated from 16.8.6
to 16.9.0
.devDependency
react-dom was updated from 16.8.6
to 16.9.0
.Your tests are passing again with this update. Explicitly upgrade to these versions π
<React.Profiler>
API for gathering performance measurements programmatically. (@bvaughn in #15172)unstable_ConcurrentMode
in favor of unstable_createRoot
. (@acdlite in #15532)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 from useEffect
, creating a loop. (@gaearon in #15180)findDOMNode
for components wrapped in <Suspense>
. (@acdlite in #15312)!important
style. (@acdlite in #15861 and #15882)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)β’ 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/
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
.Your tests are passing again with this update. Explicitly upgrade to these versions π
Object.is
instead of inline polyfill, when available. (@ku8ar in #16212)postMessage
loop with short intervals instead of attempting to align to frame boundaries with requestAnimationFrame
. (@acdlite in #16214)β’ react: https://unpkg.com/react@16.10.0/umd/
β’ react-art: https://unpkg.com/react-art@16.10.0/umd/
β’ react-dom: https://unpkg.com/react-dom@16.10.0/umd/
β’ react-is: https://unpkg.com/react-is@16.10.0/umd/
β’ react-test-renderer: https://unpkg.com/react-test-renderer@16.10.0/umd/
β’ scheduler: https://unpkg.com/scheduler@0.16.0/umd/
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
.Your tests are passing again with this update. Explicitly upgrade to these versions π
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
.Your tests are passing again with this update. Explicitly upgrade to these versions π
β’ 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
.Your tests are passing again with this update. Explicitly upgrade to these versions π
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
.Your tests are passing again with this update. Explicitly upgrade to these versions π
β’ react: https://unpkg.com/react@16.12.0/umd/
β’ react-art: https://unpkg.com/react-art@16.12.0/umd/
β’ react-dom: https://unpkg.com/react-dom@16.12.0/umd/
β’ react-is: https://unpkg.com/react-is@16.12.0/umd/
β’ react-test-renderer: https://unpkg.com/react-test-renderer@16.12.0/umd/
β’ scheduler: https://unpkg.com/scheduler@0.18.0/umd/
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
.Your tests are passing again with this update. Explicitly upgrade to these versions π
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)devDependency
react was updated from 16.13.0
to 16.13.1
.devDependency
react-dom was updated from 16.13.0
to 16.13.1
.Your tests are passing again with this update. Explicitly upgrade to these versions π
There have been updates to the react monorepo:
devDependency
react was updated from16.5.2
to16.6.0
.devDependency
react-dom was updated from16.5.2
to16.6.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 could not complete due to an error ([Details](https://travis-ci.org/rxreact/signal-connect/builds/445414469?utm_source=github_status&utm_medium=notification)).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: