Skip to content

Way to 0.4.14 #51

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

Merged
merged 7 commits into from
Apr 16, 2016
Merged

Way to 0.4.14 #51

merged 7 commits into from
Apr 16, 2016

Conversation

syrusakbary
Copy link
Member

This PR reflects all the commit changes done in the GraphQL-js implementation.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.6%) to 98.206% when pulling d3e11dc on releases/0.4.14 into cab838c on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.6%) to 98.206% when pulling 608ef09 on releases/0.4.14 into cab838c on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.02%) to 98.812% when pulling 027c405 on releases/0.4.14 into cab838c on master.

@syrusakbary syrusakbary merged commit 13b55d9 into master Apr 16, 2016
@Globegitter
Copy link

@syrusakbary Loving the effort of bringing graphql-core up to the latest spec. But it seems you missed out on one PR: graphql/graphql-js@3d27953 for 0.4.14. Do you think it is possible to add that?

@ProjectCheshire ProjectCheshire deleted the releases/0.4.14 branch June 2, 2019 18:40
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.

3 participants