Skip to content
This repository has been archived by the owner on Oct 27, 2020. It is now read-only.

An in-range update of react-test-renderer is breaking the build 🚨 #139

Open
greenkeeper bot opened this issue Mar 29, 2018 · 4 comments
Open

An in-range update of react-test-renderer is breaking the build 🚨 #139

greenkeeper bot opened this issue Mar 29, 2018 · 4 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 29, 2018

☝️ 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.

Branch Build failing 🚨
Dependency react-test-renderer
Current Version 16.2.0
Type devDependency

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

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
Copy link
Contributor Author

greenkeeper bot commented Mar 29, 2018

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.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 4, 2018

Version 16.3.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v16.3.1

16.3.1 (April 3, 2018)

React

React DOM

Create Subscription

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 16, 2018

Version 16.3.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v16.3.2

16.3.2 (April 16, 2018)

React

  • Improve the error message when passing null or undefined to React.cloneElement. (@nicolevy in #12534)

React DOM

  • Fix an IE crash in development when using <StrictMode>. (@bvaughn in #12546)
  • Fix labels in User Timing measurements for new component types. (@bvaughn in #12609)
  • Improve the warning about wrong component type casing. (@nicolevy in #12533)
  • Improve general performance in development mode. (@gaearon in #12537)
  • Improve performance of the experimental unstable_observedBits API with nesting. (@gaearon in #12543)

React Test Renderer

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 24, 2018

Version 16.4.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v16.4.0

React

React DOM

  • Add support for the Pointer Events specification. (@philipp-spiess in #12507)
  • Properly call getDerivedStateFromProps() regardless of the reason for re-rendering. (@acdlite in #12600 and #12802)
  • Fix a bug that prevented context propagation in some cases. (@gaearon in #12708)
  • Fix re-rendering of components using forwardRef() on a deeper setState(). (@gaearon in #12690)
  • Fix some attributes incorrectly getting removed from custom element nodes. (@airamrguez in #12702)
  • Fix context providers to not bail out on children if there's a legacy context provider above. (@gaearon in #12586)
  • Add the ability to specify propTypes on a context provider component. (@nicolevy in #12658)
  • Fix a false positive warning when using react-lifecycles-compat in <StrictMode>. (@bvaughn in #12644)
  • Warn when the forwardRef() render function has propTypes or defaultProps. (@bvaughn in #12644)
  • Improve how forwardRef() and context consumers are displayed in the component stack. (@sophiebits in #12777)
  • Change internal event names. This can break third-party packages that rely on React internals in unsupported ways. (@philipp-spiess in #12629)

React Test Renderer

  • Fix the getDerivedStateFromProps() support to match the new React DOM behavior. (@koba04 in #12676)
  • Fix a 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)
  • Shallow renderer now ignores setState() updaters that return null or undefined. (@koba04 in #12756)

React ART

  • Fix reading context provided from the tree managed by React DOM. (@acdlite in #12779)

React Call Return (Experimental)

  • This experiment was deleted because it was affecting the bundle size and the API wasn't good enough. It's likely to come back in the future in some other form. (@gaearon in #12820)

React Reconciler (Experimental)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0 participants