[meta] Release 0.5.0

[trojanowski]

I'm going to introduce a few breaking changes in the next release of react-apollo-hooks:

• useMutation returns tuple with result data ([alternative] feat(useMutation): returns tuple with result data #135, based on BREAKING CHANGE: useMutation returns tuple with result #93)
• use setOptions for updating query ([wip] fix(useQuery): use setOptions for updating query #134)
• fix behavior of getMarkupFromTree (handling server side graphql errors without suspense #65)

Please note that the first one has the most significant impact. The other ones are breaking only in some subtle scenarios.

[emadow]

Thanks for your work here. Really looking forward to this release!

[lukasluecke]

Also looking forward to the release 🚀 - is there any ETA for at least an experimental release? Tried building the PR-version myself but got some weird issues with apollo 😕

[SimenB]

Would be lovely to release the mutation change without waiting for the other PRs (if they're gonna take a week or more) 🙏

[trojanowski]

@SimenB I just published an alpha version of 0.5.0 with #135 (the mutation change) merged-in. It's available as react-apollo-hooks@alpha.

[SimenB]

That's awesome, thanks!

EDIT: Works perfectly in our project, allowing us to remove the last of the render props components 🎉

[lukasluecke]

@evert-smit You need to wrap toggleTask like [toggleTask] - this is exactly the change that #135 entails. The README will only be updated in master once it's merged there, but you can check out the README in the PR for the correct code.

[TimFL]

Are there any plans to finish this release up or is this project dead due to the (I hope soonish?) release of hooks in the official apollo client?

[trojanowski]

I decided to release version 0.5.0 with useMutation changes and fixes for TypeScript and Apollo Client 2.6.0. I didn't have time for #134 - if someone needs it and could continue the work, then I'd merge it (but maybe "@apollo/react-hooks" is a better alternative in that case). :)