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

chore(deps): lock react-addons-test-utils #1248

Closed

Conversation

Dattaya
Copy link
Member

@Dattaya Dattaya commented Nov 17, 2016

Trying to fix #1246

@coveralls
Copy link

coveralls commented Nov 17, 2016

Coverage Status

Coverage remained the same at 98.605% when pulling ad5afb9 on Dattaya:lock-react-addons-test-utils into 33485f4 on mxstbr:dev.

@Dattaya
Copy link
Member Author

Dattaya commented Nov 17, 2016

Something installs react-addons-test-utils@15.4 and we're bumping into this bug: facebook/react#8314
I don't understand why recent pull requests pass Travis build but fail AppVeyor. On my Windows machine everything works fine.

@Dattaya Dattaya mentioned this pull request Nov 17, 2016
2 tasks
@gihrig
Copy link
Contributor

gihrig commented Nov 17, 2016

According to this comment, it's not so much a bug as a breaking change in an un-tracked (transient) dependency (react-addons-test-utils).

I have no problem with adding react-addons-test-utils to package.json, but now that react 15.4 has shipped, we should lock react, react-dom and react-addons-test-utils at 15.4. No?

@Dattaya
Copy link
Member Author

Dattaya commented Nov 17, 2016

Yes, if the other packages work fine with React 15.4, it's better to update libraries from React ecosystem instead of merging this fix. I might need to create another fix for the master branch in case it's affected too, it seems like it is judging from #1246

@Dattaya
Copy link
Member Author

Dattaya commented Nov 17, 2016

...or update dependencies there too if it's acceptable.

@gihrig
Copy link
Contributor

gihrig commented Nov 17, 2016

Master branch includes a yarn.lock, but yarn is not an official (required) dependency of react-boilerplate (yet).

Maybe better to release react-boilerplate 3.3.4 to master with react-addons-test-utils as a dependency. That would be my preference over a hot fix to 3.3.3 master.

@mxstbr, what other open PRs (if any) would you like to see included in 3.3.4?

@gihrig
Copy link
Contributor

gihrig commented Nov 20, 2016

@Dattaya I have included react-addons-test-utils@15.4.0 in this week's dependency update #1252. So I'm closing this PR as the issue is fixed in #1252 for dev and IMHO, master should be fixed be fixed by a version update to 3.3.4. I have also closed #1246.

Thank you for taking the time time to research this issue and open the PR! 😄

@gihrig gihrig closed this Nov 20, 2016
@Dattaya Dattaya deleted the lock-react-addons-test-utils branch November 22, 2016 13:08
@lock
Copy link

lock bot commented May 29, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants