update graphql peerdep

[graingert]

This is a fixed version of #407

[IvanGoncharov]

@graingert Great 👍
Can you also fix npm test?
Updating flow-bin will solve all Flow errors.
You also need to update error messages inside tests:
https://travis-ci.org/graphql/express-graphql/jobs/329899395#L827

[graingert]

Was hoping it would just pass. Will have a fiddle locally

[graingert]

@IvanGoncharov I also had to update eslint.

[graingert]

@IvanGoncharov can you also have a look at my other PRs: #410 #409

[IvanGoncharov]

@graingert Great 👍
Now we need to wait for someone with commit rights to merge this PR.

@leebyron Can you please take a look?

[IvanGoncharov]

@leebyron This is super simple PR that just add support for ^0.12.0 vesions of graphql-js and fix a few test. At the same time it blocks a lot of people including myself from upgrading to the new version of graphql.
Can you please take a look?

[IvanGoncharov]

@leebyron Now that 0.13 is published can you please merge this PR and also add 0.13 to peerDependencies?

Without this change express-graphql is unusable 😭

[IvanGoncharov]

@graingert Merged 🎉 Thank you for PR and sorry for the delay.
I will try to make release ASAP.

[graingert]

Woops this is a bit too late 0.13 came out.

…

On 15 Feb 2018 15:09, "Ivan Goncharov" ***@***.***> wrote: @graingert <https://github.com/graingert> Merged 🎉 Thank you for PR and sorry for the delay. I will try to make release ASAP. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#411 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAZQTAsllWPNKL02kGzlRYkbxCQol5zQks5tVEiXgaJpZM4RhcCZ> .

[IvanGoncharov]

@graingert I'm working on it.
I just got commits rights to this repo so I want to make a new release including all simple PRs.

[graingert]

Kay

…

On 15 Feb 2018 23:48, "Ivan Goncharov" ***@***.***> wrote: @graingert <https://github.com/graingert> I'm working on it. I just got commits rights to this repo so I want to make a new release including all simple PRs. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#411 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAZQTH3IIcyLrkIsvdCXEE8bEYzRTyyVks5tVMJigaJpZM4RhcCZ> .

[graingert]

Any chance of a graphql monorepo? So versions can be updated and tested in lockstep?

…

On 15 Feb 2018 23:49, "Thomas Grainger" ***@***.***> wrote: Kay On 15 Feb 2018 23:48, "Ivan Goncharov" ***@***.***> wrote: > @graingert <https://github.com/graingert> I'm working on it. > I just got commits rights to this repo so I want to make a new release > including all simple PRs. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#411 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAZQTH3IIcyLrkIsvdCXEE8bEYzRTyyVks5tVMJigaJpZM4RhcCZ> > . >

[IvanGoncharov]

@graingert It's planned to release graphql@14.0.0, so updating peer dependency will be required only after breaking changes: graphql/graphql-js#1005

[IvanGoncharov]

@graingert 📦 v0.6.12 released with support for graphql v0.12.x and v0.13.x.