search

sandiegojs / sdjs-speaker-pipeline

Web application to apply a workflow for organizing speakers for events.
MIT License
2 stars 29 forks source link

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

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

There have been updates to the react monorepo:

🚨 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: build-job:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/sandiegojs/sdjs-speaker-pipeline/408?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
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/react@16.10.2/umd/
• react-art: https://unpkg.com/react-art@16.10.2/umd/
• react-dom: https://unpkg.com/react-dom@16.10.2/umd/
• react-is: https://unpkg.com/react-is@16.10.2/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.10.2/umd/
• scheduler: https://unpkg.com/scheduler@0.16.2/umd/

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 5 years ago

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

greenkeeper[bot] commented 5 years ago

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/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/

greenkeeper[bot] commented 5 years ago

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

greenkeeper[bot] commented 4 years ago

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

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[bot] commented 4 years ago

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

Release Notes for 16.13.1 (March 19, 2020)

React DOM

  • Fix bug in legacy mode Suspense where effect clean-up functions are not fired. This only affects users who use Suspense for data fetching in legacy mode, which is not technically supported. (@acdlite in #18238)
  • Revert warning for cross-component updates that happen inside class render lifecycles (componentWillReceiveProps, shouldComponentUpdate, and so on). (@gaearon in #18330)

Artifacts