Open greenkeeper[bot] opened 6 years ago
After pinning to 16.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
Fragment
. (@heikkilamarko in #12504)setState()
in constructor. (@gaearon in #12532)getDerivedStateFromProps()
not getting applied in some cases. (@acdlite in #12528)Your tests are still failing with this version. Compare the changes 🚨
null
or undefined
to React.cloneElement
. (@nicolevy in #12534)<StrictMode>
. (@bvaughn in #12546)unstable_observedBits
API with nesting. (@gaearon in #12543)Your tests are still failing with this version. Compare the changes 🚨
React.unstable_Profiler
component for measuring performance. (@bvaughn in #12745)getDerivedStateFromProps()
regardless of the reason for re-rendering. (@acdlite in #12600 and #12802)forwardRef()
on a deeper setState()
. (@gaearon in #12690)propTypes
on a context provider component. (@nicolevy in #12658)react-lifecycles-compat
in <StrictMode>
. (@bvaughn in #12644)forwardRef()
render function has propTypes
or defaultProps
. (@bvaughn in #12644)forwardRef()
and context consumers are displayed in the component stack. (@sophiebits in #12777)getDerivedStateFromProps()
support to match the new React DOM behavior. (@koba04 in #12676)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)setState()
updaters that return null
or undefined
. (@koba04 in #12756)
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 16.3.0 of react-test-renderer was just published.
This version is covered by your current version range and after updating it in your project the build failed.
react-test-renderer 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/gursesl/cherrypie/builds/360019445?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: