Skip to content
This repository has been archived by the owner on Aug 19, 2022. It is now read-only.

react-dom@15.2.0 breaks build 🚨 #760

Merged
merged 1 commit into from
Aug 9, 2016
Merged

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

react-dom just published its new version 15.2.0.

State Failing tests 🚨
Dependency react-dom
New version 15.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As react-dom is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


GitHub Release

React

  • Add error codes to production invariants, with links to the view the full error text. (@keyanzhang in #6948)
  • Include component stack information in PropType validation warnings. (@spicyj in #6771)
  • Include component stack information in key warnings. (@keyanzhang in #6799)
  • Stop validating props at mount time, only validate at element creation. (@keyanzhang in #6823)
  • New invariant providing actionable error in missing instance case. (@yungsters in #6990)
  • Add React.PropTypes.symbol to support ES2015 Symbols as props. (@puradox in #6377)
  • Fix incorrect coercion of ref or key that are undefined in development (@gaearon in #6880)
  • Fix a false positive when passing other element’s props to cloneElement (@ericmatthys in #6268)

React DOM

  • Add warning for unknown properties on DOM elements. (@jimfb in #6800, @gm758 in #7152)
  • Properly remove attributes from custom elements. (@grassator in #6748)
  • Fix invalid unicode escape in attribute name regular expression. (@nbjahan in #6772)
  • Add onLoad handling to <link> element. (@roderickhsiao in #6815)
  • Add onError handling to <source> element. (@wadahiro in #6941)
  • Handle value and defaultValue more accurately in the DOM. (@jimfb in #6406)
  • Fix events issue in environments with mutated Object.prototype. (@Weizenlol in #6886)
  • Fix issue where is="null" ended up in the DOM in Firefox. (@darobin in #6896)
  • Improved performance of text escaping by using escape-html. (@aickin in #6862)
  • Fix issue with dangerouslySetInnerHTML and SVG in Internet Explorer. (@joshhunt in #6982)
  • Fix issue with <textarea> placeholders. (@jimfb in #7002)
  • Fix controlled vs uncontrolled detection of <input type="radio"/>. (@jimfb in #7003)
  • Improve performance of updating text content. (@trueadm in #7005)
  • Ensure controlled <select> components behave the same on initial render as they do on updates. (@yiminghe in #5362)

React Perf Add-on

React CSSTransitionGroup Add-on

React Native Renderer

  • Dependencies on React Native modules use CommonJS requires instead of providesModule. (@davidaurelio in #6715)

This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@coveralls
Copy link

coveralls commented Jul 1, 2016

Coverage Status

Coverage remained the same at 96.26% when pulling a2a3d25 on greenkeeper-react-dom-15.2.0 into 7be72ab on master.

@coveralls
Copy link

coveralls commented Jul 5, 2016

Coverage Status

Coverage remained the same at 96.26% when pulling db9c56a on greenkeeper-react-dom-15.2.0 into 3c9f4d6 on master.

@ianobermiller ianobermiller force-pushed the greenkeeper-react-dom-15.2.0 branch 4 times, most recently from e8fb0e7 to 624faed Compare July 6, 2016 16:29
@coveralls
Copy link

coveralls commented Jul 6, 2016

Coverage Status

Coverage remained the same at 96.26% when pulling 624faed on greenkeeper-react-dom-15.2.0 into f1a8d3a on master.

@coveralls
Copy link

coveralls commented Jul 6, 2016

Coverage Status

Coverage remained the same at 96.26% when pulling 624faed on greenkeeper-react-dom-15.2.0 into f1a8d3a on master.

@coveralls
Copy link

coveralls commented Jul 26, 2016

Coverage Status

Coverage remained the same at 96.254% when pulling d0f4afd on greenkeeper-react-dom-15.2.0 into 309ea5b on master.

@ianobermiller ianobermiller force-pushed the greenkeeper-react-dom-15.2.0 branch 2 times, most recently from 6f17dfb to 8818cbf Compare August 8, 2016 22:50
@coveralls
Copy link

coveralls commented Aug 8, 2016

Coverage Status

Coverage remained the same at 96.254% when pulling 8818cbf on greenkeeper-react-dom-15.2.0 into 3d8dd47 on master.

@coveralls
Copy link

coveralls commented Aug 8, 2016

Coverage Status

Coverage remained the same at 96.254% when pulling 8818cbf on greenkeeper-react-dom-15.2.0 into 3d8dd47 on master.

@coveralls
Copy link

coveralls commented Aug 9, 2016

Coverage Status

Coverage remained the same at 96.254% when pulling de73743 on greenkeeper-react-dom-15.2.0 into 452a26c on master.

@alexlande alexlande merged commit f53cb8c into master Aug 9, 2016
@alexlande alexlande deleted the greenkeeper-react-dom-15.2.0 branch August 9, 2016 17:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants