Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of react is breaking the build 🚨 #12

Open
greenkeeper bot opened this issue Dec 20, 2018 · 2 comments
Open

An in-range update of react is breaking the build 🚨 #12

greenkeeper bot opened this issue Dec 20, 2018 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 20, 2018

There have been updates to the react monorepo:

    • The dependency react was updated from 16.6.3 to 16.7.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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v16.7.0

React DOM

  • Fix performance of React.lazy for large numbers of lazily-loaded components. (@acdlite in #14429)
  • Clear fields on unmount to avoid memory leaks. (@trueadm in #14276)
  • Fix bug with SSR and context when mixing react-dom/server@16.6 and react@<16.6. (@gaearon in #14291)
  • Fix a performance regression in profiling mode. (@bvaughn in #14383)

Scheduler (Experimental)

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 Dec 20, 2018

After pinning to 16.6.3 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 Feb 6, 2019

  • The dependency react was updated from 16.7.0 to 16.8.0.
  • The dependency react-dom was updated from 16.7.0 to 16.8.0.
  • The devDependency react-test-renderer was updated from 16.7.0 to 16.8.0.

Your tests are still failing with these versions. Compare changes

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

No branches or pull requests

0 participants