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

[Snyk] Upgrade react from 15.6.1 to 15.6.2 #2

Merged
merged 1 commit into from
Dec 13, 2019

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Sep 4, 2019

Snyk have raised this PR to upgrade react from 15.6.1 to 15.6.2.

  • The recommended version is 9 versions ahead of your current version.
  • The recommended version was released 2 years ago, on 2017-09-26.
Release notes
  • 15.6.2 - 2017-09-26

    15.6.2 (September 25, 2017)

    All Packages

    • Switch from BSD + Patents to MIT license

    React DOM

    • Fix a bug where modifying document.documentMode would trigger IE detection in other browsers, breaking change events. (@aweary in #10032)
    • CSS Columns are treated as unitless numbers. (@aweary in #10115)
    • Fix bug in QtWebKit when wrapping synthetic events in proxies. (@walrusfruitcake in #10115)
    • Prevent event handlers from receiving extra argument in development. (@aweary in #10115)
    • Fix cases where onChange would not fire with defaultChecked on radio inputs. (@jquense in #10156)
    • Add support for controlList attribute to DOM property whitelist (@nhunzaker in #9940)
    • Fix a bug where creating an element with a ref in a constructor did not throw an error in development. (@iansu in #10025)
  • 15.6.1 - 2017-06-15

    15.6.1 (June 14, 2017)

    React DOM

from react GitHub Release Notes


🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@jakeherp jakeherp merged commit 7f86c73 into master Dec 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants