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

Upgrade to react 16 #57

Merged
merged 3 commits into from
Nov 15, 2017
Merged

Upgrade to react 16 #57

merged 3 commits into from
Nov 15, 2017

Conversation

reidmit
Copy link
Contributor

@reidmit reidmit commented Oct 3, 2017

We've made changes to the package.json to allow react-tether to work with React v16.0.0

this should fix #56

PS: we aren't sure if the yarn.lock is necessary for the upgrade.

reidmit and others added 2 commits October 3, 2017 10:25
Signed-off-by: Stephane Jolicoeur <sjolicoeur@pivotal.io>
Signed-off-by: Reid Mitchell <rmitchell@pivotal.io>
package.json Outdated
@@ -34,8 +34,8 @@
"tether": "^1.3.7"
},
"peerDependencies": {
"react": "^0.14.0 || ^15.0.0",
"react-dom": "^0.14.0 || ^15.0.0"
"react": "^16.0.0",
Copy link
Contributor

@rafeememon rafeememon Oct 3, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Support for 0.14 and 15.x probably shouldn't be removed unless there is a breaking change

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rafeememon ok will fix this ASAP.

…aking change

Signed-off-by: Reid Mitchell <rmitchell@pivotal.io>
@seanmheff
Copy link

LGTM!

@gmathieu
Copy link

Is there anything blocking this PR?

@sjolicoeur
Copy link

@rafeememon we made the necessary change, is it possible to have the PR merged and a new release?

@seanmheff
Copy link

Any update on this?

@ghost
Copy link

ghost commented Oct 28, 2017

It's not going to happen until #58 is fixed

@augbog
Copy link

augbog commented Nov 2, 2017

@souporserious are we really blocked on merging this because there isn't a new maintainer assigned yet? I just want to verify

@danreeves danreeves self-assigned this Nov 14, 2017
@danreeves danreeves merged commit f82016a into danreeves:master Nov 15, 2017
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.

React 16 Support
7 participants