Create a new release

[LegNeato]

It's about time to push out a new release. I want to automate a bit more of the process as well.

We probably need the book updating working too.

[theduke]

We have some breaking changes merged into master but I think they are so small that they don't really merit a version bump yet.

We should probably cherry-pick the non-breaking stuff into a 0.11 branch and release from there.

[theduke]

Well, actually, #312 is really minor and ScalarValue is still there, only deprecated, so I think master should be fine.

[LegNeato]

I landed changes to release automation. I think we want #353 and then we can do a release. We should do a minor (not patch) version bump as we increased the minimum rust version.

[theduke]

If we are doing a minor now we should also include #333 since it provide a significant usability improvement. The syn version bump also requires a minor version.

That does bump rust requirement to 1.34, but only if you use certain attributes on field resolvers with the new impl_object. Considering the big improvement I think it's worth it.

That way we won't need another minor bump until async support.
Better one dependency bump than two in a relatively short time.

[LegNeato]

Hmmm, that is a huge change. I'd prefer to do a release with current state and then land that, have it sit in master for a bit, and then cut another one.

[theduke]

It's a big change but not a user visible one right away since everyone will still be on the old macro. Also I've converted one large and two smallish projects and all works fine.

It wouldn't see much testing on master anyway.

[LegNeato]

I don't think we need to wait on the book here. Do you want to run a release or shall I?

[theduke]

Can do, but since you did all the work on the releasing tool, you should have the honors of breaking it in.

[theduke]

@LegNeato actually I'd love to get #355 in as well since it's breaking.

[LegNeato]

Ok, I'll do a release later tonight! Probably best for me to do it so if automation breaks I can fix it

[theduke]

@LegNeato please also check Gitter, I sent you a message with a nice surprise.

[LegNeato]

Juniper 0.12.0 is out!

Automation seemed to work well. cargo-release is pretty brittle, so I added some additional directions to RELEASING.md suggesting a clean checkout.

[theduke]

@LegNeato for future reference, what was brittle about it?

[LegNeato]

The cargo-release parts error out when pushing to git if your repo's git remote branch isn't in sync with upstream/master.

A clean clone with this repo as origin makes all those issues impossible, so that's what I added to the docs.