Bump graphql-core from 2.1.0 to 3.1.6

[dependabot]

Bumps graphql-core from 2.1.0 to 3.1.6.

Release notes

Sourced from graphql-core's releases.

v3.1.6

Patch release GraphQL-core v3.1.6, based on GraphQL.js v15.5.1.

This release includes only some minor changes and improvements.

v3.1.5

Patch release GraphQL-core v3.1.5, based on GraphQL.js v15.4.0.

This release includes the following changes and imrovements:

• Default parse_literal of GraphQLScalarType now handles variables
• build_ast_schema now matches order of default types and directives
• Return formatted errors in formatted execution result (fixes #129)
• The is_deprecated property is now deprecated itself
• Input fields and arguments can now be marked as deprecated
• Handle case when MapAsyncIterator is cancelled (#131)
• Improve return type for complete_list_value (#132)
• Replace resolved types in lexicographic schema sort
• EventEmitter helper class has been replaces by SimplePubSub
• print_ast now breaks arguments over multiple lines

Special thanks to @​cancan101, @​mlorenzana, @​wuyuanyi135 for contributing.

v3.1.4

Patch release GraphQL-core v3.1.4, based on GraphQL.js v15.3.0.

This release fixes issues #125 and #126 regarding enum values.

Thanks to @​dkbarn for reporting the problem.

v3.1.3

Patch release GraphQL-core v3.1.3, based on GraphQL.js v15.2.0.

This release includes the following improvements:

• Python 3.9 is now officially suported by GraphQL-core.
• build_schema: allow to reference introspection types
• Custom validation rules for "no schema introspection" and "no deprecated"
• Added execute_sync() as synchronous version of execute()
• Support deep copy of GraphQL schema (#100)
• build_ast_schema now sets internal enum values (#111)
• Do not double-wrap resolver errors any more (#106)
• Use newer Sphinx version, fix for various autodoc issues (#104)
• Fix example in docstring of GraphQLUnionType (#105)
• Let default resolver check for Mapping instead of dict (#102)

Thanks to everyone who helped with their feedback, particularly

@​berekuk, @​charmasaur, @​Checho3388, @​jstlaurent and @​pmantica1.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #873.