Update graphql to the latest version 🚀#117
Conversation
Codecov Report
@@ Coverage Diff @@
## master #117 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 6 6
Lines 133 133
=====================================
Hits 133 133Continue to review full report at Codecov.
|
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:
VariablesDefaultValueAllowedvalidation rule, andProvidedNonNullArgumentsbecameProvidedRequiredArguments(#1274)onOperation,onFragment, andonField(#1385, #1429)GraphQL*Configare now exact types (#1391, #1443)BreakingChangeTypeandDangerousChangeTypefor detecting adding args and input fields changed name (#1492)formatErrorAPI changed for error message extensions. To upgrade without changing existing server responses, wrapgraphql'sformatError:New:
extendSchemaextended with spec-compliant SDL extensions (#1373, #1392, #1441)symbol.toStringTagsupport (#1297)getOperationRootType(schema, operationAST)(#1345)validateSchemaworks with Schema extensions (#1410)validateworks on SDL definitions (#1438, #1383)experimentalVariableDefinitionDirectivesflag (#1437, #1454)isDefinitionNodeandisTypeSystemDefinitionNode(#1459)isRequiredArgumentandisRequiredInputFieldpredicates (#1463)Fixed:
introspectionFromSchemahas default options (#1408)buildSchemamemory leaks and infinite recursion fixed (#1417, #1427)watchcommand 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 🌴