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

Open
greenkeeper bot opened this issue Oct 23, 2019 · 4 comments
Open

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

greenkeeper bot opened this issue Oct 23, 2019 · 4 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 23, 2019

There have been updates to the react monorepo:

    • 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.

🚨 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

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/react@16.11.0/umd/
• react-art: https://unpkg.com/react-art@16.11.0/umd/
• react-dom: https://unpkg.com/react-dom@16.11.0/umd/
• react-is: https://unpkg.com/react-is@16.11.0/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.11.0/umd/
• scheduler: https://unpkg.com/scheduler@0.17.0/umd/

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 Oct 23, 2019

After pinning to 16.10.2 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 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.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 29, 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.

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
Contributor 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.

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