Update graphql to the latest version 🚀#11
Conversation
Version 0.10.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 30 commits.
There are 30 commits in total. See the full diff |
Version 0.10.3 just got published.Update to this version instead 🚀 Release Notesv0.10.3New:
Fixed:
|
Version 0.10.4 just got published.Update to this version instead 🚀 CommitsThe new version differs by 46 commits.
There are 46 commits in total. See the full diff |
Version 0.10.5 just got published. |
Version 0.11.0 just got published.Update to this version instead 🚀 Release Notesv0.11.0Breaking
Spec compliance
Fixes
ChangesCommitsThe new version differs by 41 commits.
There are 41 commits in total. See the full diff |
Version 0.11.1 just got published. |
Version 0.11.2 just got published.Update to this version instead 🚀 Release Notesv0.11.2Fixes
CommitsThe new version differs by 10 commits.
See the full diff |
Version 0.11.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Version 0.11.4 just got published.Update to this version instead 🚀 Release Notesv0.11.4New:
Fixes:
CommitsThe new version differs by 7 commits.
See the full diff |
Version 0.11.5 just got published.Update to this version instead 🚀 Release Notesv0.11.5Fixes
|
Version 0.11.6 just got published. |
Version 0.11.7 just got published.Update to this version instead 🚀 Release Notesv0.11.7Fixes:
|
Version 0.12.0 just got published.Update to this version instead 🚀 Release Notesv0.12.0RELEASE NOTES COMING SOON CommitsThe new version differs by 109 commits.
There are 109 commits in total. See the full diff |
Version 0.12.1 just got published.Update to this version instead 🚀 Release Notesv0.12.1Flow Type Fixes: CommitsThe new version differs by 5 commits.
See the full diff |
Version 0.12.2 just got published.Update to this version instead 🚀 Release Notesv0.12.2Fixes: |
Version 0.12.3 just got published.Update to this version instead 🚀 Release Notesv0.12.3Fixes:
|
Version 0.13.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 44 commits.
There are 44 commits in total. See the full diff |
Version 0.13.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 0.13.2 just got published.Update to this version instead 🚀 Release Notesv0.13.2New: Fixes: CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Version 14.0.0-rc.1 just got published.Update to this version instead 🚀 Release Notesv14.0.0-rc.1NOTE Breaking:
New:
Fixed: CommitsThe new version differs by 56 commits.
There are 56 commits in total. See the full diff |
Version 14.0.0-rc.2 just got published.Update to this version instead 🚀 Release Notesv14.0.0-rc.2Breaking change reverted:
|
Version 14.0.0 just got published.Update to this version instead 🚀 Release Notesv14.0.0Breaking:
New:
Fixed:
Deprecated: These will be removed in v15 |
Version 14.0.1 just got published.Update to this version instead 🚀 Release Notesv14.0.1(Something went wrong during release, this version has been unpublished) |
Version 14.0.2 just got published.Update to this version instead 🚀 Release Notesv14.0.2Fixes:
|
Version 0.10.0 of graphql just got published.
The version 0.10.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of graphql.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v0.10.0New
isValidValue()andisValidLiteral()added to Scalar and enum types (#861).graphql()may now take aSourceobject, in addition to the existing support forstring(#866).graphql()may now take an object with named parameters (#867).Breaking
Intvalues toInt(#837).Fixes
GraphQLErrorstack trace includes error message (#718).Commits
The new version differs by 57 commits.
797e7e30.10.0845a45bMerge pull request #878 from gabelevi/flowfe5f544Flow v0.47.0 finds 3 errors in master. This is important to fix, because the87b24eeFreshen yarn.lock704a97dMerge pull request #877 from graphql/greenkeeper/mocha-3.4.20f186dechore(package): update mocha to version 3.4.21ff4932Freshen yarn.locke989de8Merge pull request #875 from graphql/greenkeeper/sane-1.7.09811d06chore(package): update sane to version 1.7.0f6f26fdHandle abrupt closing in mapAsyncIterator() (#870)50504b9remove unnecessary null arguments in test562ceadAllow providing an object of arguments to graphql(). (#867)1b41959Allow graphql() to accept a Source instance. (#866)bf352a8json is hard5510c75Allow providing custom default field resolver. (#865)There are 57 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴