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

react-dom@15.1.0 breaks build 🚨 #3

Closed
wants to merge 1 commit into from

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello πŸ‘‹

🚨🚨🚨

react-dom just published its new version 15.1.0, which is covered by your current version range. After updating it in your project the build went from success to failure.

This means your software is now malfunctioning, because of this update. Use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


GitHub Release

React

  • Ensure we're using the latest object-assign, which has protection against a non-spec-compliant native Object.assign. (@zpao in #6681)
  • Add a new warning to communicate that props objects passed to createElement must be plain objects. (@richardscarrott in #6134)
  • Fix a batching bug resulting in some lifecycle methods incorrectly being called multiple times. (@spicyj in #6650)

React DOM

  • Fix regression in custom elements support. (@jscissr in #6570)
  • Stop incorrectly warning about using onScroll event handler with server rendering. (@Aweary in #6678)
  • Fix grammar in the controlled input warning. (@jakeboone02 in #6657)
  • Fix issue preventing <object> nodes from being able to read <param> nodes in IE. (@syranide in #6691)
  • Fix issue resulting in crash when using experimental error boundaries with server rendering. (@jimfb in #6694)
  • Add additional information to the controlled input warning. (@borisyankov in #6341)

React Perf Add-on

  • Completely rewritten to collect data more accurately and to be easier to maintain. (@gaearon in #6647, #6046)

React Native Renderer


This pull request was created by greenkeeper.io.
It keeps your software up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚑

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 91aa2fb on greenkeeper-react-dom-15.1.0 into 7e3dd42 on master.

@perrin4869 perrin4869 closed this Jun 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants