-
Notifications
You must be signed in to change notification settings - Fork 79
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
Update graphql to the latest version 🚀 #167
base: master
Are you sure you want to change the base?
Conversation
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:
|
Update to this version instead 🚀 Release Notes for v14.1.0New: Fixes: CommitsThe new version differs by 109 commits.
There are 109 commits in total. See the full diff |
Update to this version instead 🚀 Release Notes for v14.2.014.2.0 (2019-03-26)Note: Updating to this release can cause new Flow errors since it adds Flow typing for New Feature 🚀
Bug Fix 🐞
Docs 📝
Polish 💅42 PRs were merged
Internal 🏠17 PRs were merged
Committers: 7
CommitsThe new version differs by 114 commits.
There are 114 commits in total. See the full diff |
Update to this version instead 🚀 Release Notes for v14.2.114.2.1 (2019-03-31)Bug Fix 🐞
|
Update to this version instead 🚀 CommitsThe new version differs by 37 commits.
There are 37 commits in total. See the full diff |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version 14.0.0 of graphql was just published.
The version 14.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of graphql.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v14.0.0Breaking:
VariablesDefaultValueAllowed
validation rule, andProvidedNonNullArguments
becameProvidedRequiredArguments
(#1274)onOperation
,onFragment
, andonField
(#1385, #1429)GraphQL*Config
are now exact types (#1391, #1443)BreakingChangeType
andDangerousChangeType
for detecting adding args and input fields changed name (#1492)formatError
API changed for error message extensions. To upgrade without changing existing server responses, wrapgraphql
'sformatError
:New:
extendSchema
extended with spec-compliant SDL extensions (#1373, #1392, #1441)symbol.toStringTag
support (#1297)getOperationRootType(schema, operationAST)
(#1345)validateSchema
works with Schema extensions (#1410)validate
works on SDL definitions (#1438, #1383)experimentalVariableDefinitionDirectives
flag (#1437, #1454)isDefinitionNode
andisTypeSystemDefinitionNode
(#1459)isRequiredArgument
andisRequiredInputField
predicates (#1463)Fixed:
introspectionFromSchema
has default options (#1408)buildSchema
memory leaks and infinite recursion fixed (#1417, #1427)watch
command fixed (#1449)validation
(#1471)Deprecated:
These will be removed in v15
introspectionQuery
, usegetIntrospectionQuery
(#1386)getDescription
, use the schema AST node to get descriptions (#1396)isValidJSValue
, usecoerceValue
(#1386)isValidLiteralValue
, use validation (#1386)FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴