search

yaodingyd / react-flickity-component

A React.js component for using @desandro's Flickity
314 stars 51 forks source link

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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 6 years ago

There have been updates to the react monorepoundefined

🚨 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 failed ([Details](https://travis-ci.org/theolampert/react-flickity-component/builds/428401969?utm_source=github_status&utm_medium=notification)).
Release Notes for v16.5.1

16.5.1 (September 13, 2018)

React

  • Improve the warning when React.forwardRef receives an unexpected number of arguments. (@andresroberto in #13636)

React DOM

  • Fix a regression in unstable exports used by React Native Web. (@aweary in #13598)
  • Fix a crash when component defines a method called isReactComponent. (@gaearon in #13608)
  • Fix a crash in development mode in IE9 when printing a warning. (@link-alex in #13620)
  • Provide a better error message when running react-dom/profiling with schedule/tracking. (@bvaughn in #13605)
  • If a ForwardRef component defines a displayName, use it in warnings. (@probablyup in #13615)

Schedule (Experimental)

  • Add a separate profiling entry point at schedule/tracking-profiling. (@bvaughn in #13605)
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:

greenkeeper[bot] commented 6 years ago

After pinning to 16.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 6 years ago

Your tests are still failing with these versions. Compare changes

Release Notes for v16.5.2

React DOM

Schedule (Experimental)

  • Renaming "tracking" API to "tracing" (@bvaughn in #13641)
  • Add UMD production+profiling entry points (@bvaughn in #13642)
  • Refactored schedule to remove some React-isms and improve performance for when deferred updates time out (@acdlite in #13582)
greenkeeper[bot] commented 6 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

greenkeeper[bot] commented 6 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v16.6.1

16.6.1 (November 6, 2018)

React DOM

  • Fallback should not remount every time a promise resolves. (@acdlite in #14083)
  • Fix bug where Suspense keeps showing fallback even after everything finishes loading. (@acdlite in #14083)
  • Fix unresolved default props in lifecycle methods of a lazy component. (@gaearon in #14112)
  • Fix bug when recovering from an error thrown during complete phase. (@gaearon in #14104)

Scheduler (Experimental)

  • Switch from deadline object to shouldYield API. (@acdlite in #14025)
greenkeeper[bot] commented 6 years ago

Your tests are still failing with these versions. Compare changes

greenkeeper[bot] commented 6 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

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)