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 🚨 #153

Open
greenkeeper bot opened this issue Sep 14, 2018 · 20 comments
Open

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

greenkeeper bot opened this issue Sep 14, 2018 · 20 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Sep 14, 2018

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
  • ci/circleci: Your tests failed on CircleCI (Details).

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. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Sep 14, 2018

After pinning to 16.5.0 your tests are passing again. Downgrade this dependency 📌.

@greenkeeper
Copy link
Author

greenkeeper bot commented Sep 19, 2018

  • The dependency react was updated from 16.5.1 to 16.5.2.
  • The dependency react-dom was updated from 16.5.1 to 16.5.2.
  • The dependency react-test-renderer was updated from 16.5.1 to 16.5.2.

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

greenkeeper bot commented Oct 24, 2018

  • The dependency react was updated from 16.5.2 to 16.6.0.
  • The dependency react-dom was updated from 16.5.2 to 16.6.0.
  • The dependency react-test-renderer was updated from 16.5.2 to 16.6.0.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 7, 2018

  • The dependency react was updated from 16.6.0 to 16.6.1.
  • The dependency react-dom was updated from 16.6.0 to 16.6.1.
  • The dependency react-test-renderer was updated from 16.6.0 to 16.6.1.

Your tests are still failing with these versions. Compare changes

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

greenkeeper bot commented Nov 13, 2018

  • The dependency react was updated from 16.6.1 to 16.6.2.
  • The dependency react-dom was updated from 16.6.1 to 16.6.2.
  • The dependency react-test-renderer was updated from 16.6.1 to 16.6.2.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 13, 2018

  • The dependency react was updated from 16.6.2 to 16.6.3.
  • The dependency react-dom was updated from 16.6.2 to 16.6.3.
  • The dependency react-test-renderer was updated from 16.6.2 to 16.6.3.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 20, 2018

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

Your tests are still failing with these versions. Compare changes

Release Notes for v16.7.0

React DOM

Scheduler (Experimental)

@greenkeeper
Copy link
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 dependency react-test-renderer was updated from 16.7.0 to 16.8.0.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 6, 2019

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

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Mar 6, 2019

  • The dependency react was updated from 16.8.3 to 16.8.4.
  • The dependency react-dom was updated from 16.8.3 to 16.8.4.
  • The dependency react-test-renderer was updated from 16.8.3 to 16.8.4.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.4

16.8.4 (March 5, 2019)

React DOM and other renderers

  • Fix a bug where DevTools caused a runtime error when inspecting a component that used a useContext hook. (@bvaughn in #14940)

@greenkeeper
Copy link
Author

greenkeeper bot commented Mar 22, 2019

  • The dependency react was updated from 16.8.4 to 16.8.5.
  • The dependency react-dom was updated from 16.8.4 to 16.8.5.
  • The dependency react-test-renderer was updated from 16.8.4 to 16.8.5.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Mar 30, 2019

  • The dependency react was updated from 16.8.5 to 16.8.6.
  • The dependency react-dom was updated from 16.8.5 to 16.8.6.
  • The dependency react-test-renderer was updated from 16.8.5 to 16.8.6.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.6

16.8.6 (March 27, 2019)

React DOM

Artifacts

@greenkeeper
Copy link
Author

greenkeeper bot commented Aug 9, 2019

  • The dependency react was updated from 16.8.6 to 16.9.0.
  • The dependency react-dom was updated from 16.8.6 to 16.9.0.
  • The dependency react-test-renderer was updated from 16.8.6 to 16.9.0.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.9.0 (August 8, 2019)

React

  • Add <React.Profiler> API for gathering performance measurements programmatically. (@bvaughn in #15172)
  • Remove unstable_ConcurrentMode in favor of unstable_createRoot. (@acdlite in #15532)

React DOM

React DOM Server

  • Fix incorrect output for camelCase custom CSS property names. (@bedakb in #16167)

React Test Utilities and Test Renderer

Artifacts

• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

@greenkeeper
Copy link
Author

greenkeeper bot commented Sep 27, 2019

  • The dependency react was updated from 16.9.0 to 16.10.0.
  • The dependency react-dom was updated from 16.9.0 to 16.10.0.
  • The dependency react-test-renderer was updated from 16.9.0 to 16.10.0.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Sep 28, 2019

  • The dependency react was updated from 16.10.0 to 16.10.1.
  • The dependency react-dom was updated from 16.10.0 to 16.10.1.
  • The dependency react-test-renderer was updated from 16.10.0 to 16.10.1.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.10.1 (September 28, 2019)

React DOM

  • Fix regression in Next.js apps by allowing Suspense mismatch during hydration to silently proceed (@sebmarkbage in #16943)

@greenkeeper
Copy link
Author

greenkeeper bot commented Oct 4, 2019

  • The dependency react was updated from 16.10.1 to 16.10.2.
  • The dependency react-dom was updated from 16.10.1 to 16.10.2.
  • The dependency react-test-renderer was updated from 16.10.1 to 16.10.2.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.10.2 (October 3, 2019)

React DOM

  • Fix regression in react-native-web by restoring order of arguments in event plugin extractors (@necolas in #16978)

Artifacts

• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

@greenkeeper
Copy link
Author

greenkeeper bot commented Oct 23, 2019

  • The dependency react was updated from 16.10.2 to 16.11.0.
  • The dependency react-dom was updated from 16.10.2 to 16.11.0.
  • The dependency react-test-renderer was updated from 16.10.2 to 16.11.0.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.11.0 (October 22, 2019)

React DOM

  • Fix mouseenter handlers from firing twice inside nested React containers. @yuanoook in #16928
  • Remove unstable_createRoot and unstable_createSyncRoot experimental APIs. (These are available in the Experimental channel as createRoot and createSyncRoot.) (@acdlite in #17088)

Artifacts

• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 15, 2019

  • The dependency react was updated from 16.11.0 to 16.12.0.
  • The dependency react-dom was updated from 16.11.0 to 16.12.0.
  • The dependency react-test-renderer was updated from 16.11.0 to 16.12.0.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 28, 2020

  • The dependency react was updated from 16.12.0 to 16.13.0.
  • The dependency react-dom was updated from 16.12.0 to 16.13.0.
  • The dependency react-test-renderer was updated from 16.12.0 to 16.13.0.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.13.0 (February 26, 2020)

React

  • Warn when a string ref is used in a manner that's not amenable to a future codemod (@lunaruan in #17864)
  • Deprecate React.createFactory() (@trueadm in #17878)

React DOM

Concurrent Mode (Experimental)

Artifacts

@greenkeeper
Copy link
Author

greenkeeper bot commented Mar 19, 2020

  • The dependency react was updated from 16.13.0 to 16.13.1.
  • The dependency react-dom was updated from 16.13.0 to 16.13.1.
  • The dependency react-test-renderer was updated from 16.13.0 to 16.13.1.

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