Release candidate GraphQL-core v3.3.0rc1, based on GraphQL.js v17.0.0rc0.

This release candidate supports Python 3.10 to 3.14.

This is a security release. It fixes two denial-of-service vulnerabilities in the validator and the parser. Upgrading is recommended for all users of the 3.3 line.

Unlike the other releases in this series, v3.3.0rc1 does not correspond to a GraphQL.js release tag. It is a security release cut while the port of GraphQL.js v17 is still in progress, so the tracked version_js deliberately remains v17.0.0rc0.

Security fixes:

• CVE-2026-75507 (GHSA-vj8h-fx38-h3vc, High) — the OverlappingFieldsCanBeMerged validation rule could be driven into quadratic and worse running time by a small, highly compressible query using repeated inline fragments, occupying a worker for minutes of CPU during validation, before any resolver runs. Validation now enforces a per-document comparison budget and aborts with a GraphQLError once it is exhausted.
• CVE-2026-75508 (GHSA-r77w-qph3-7vf8, High) — comment tokens were allocated and retained but not counted toward the parser's max_tokens limit, so a comment-padded document could bypass the limit while allocating one token object per comment. max_tokens now counts every token the parser consumes, including skipped comments.

Please note the two behaviour changes this implies:

• A pathological query that previously validated — slowly — now produces a validation error. Realistic queries stay far below the limit, which defaults to 250,000 field comparisons and can be adjusted by assigning to graphql.validation.rules.overlapping_fields_can_be_merged.MAX_FIELD_COMPARISONS.
• Comments now count toward max_tokens, so a comment-heavy document that was previously accepted may now be rejected. If you parse documents with substantial comments and set max_tokens, you may need to raise the limit. The token_count of a parsed document now includes comments as well.

Both limits complement, but do not replace, a request body-size limit applied to the decompressed request body in your web framework.

Apart from these, there are no breaking changes after the last release candidate 3.3.0rc0.

Other notable changes:

• Incremental delivery (@defer and @stream) has been re-implemented on a new work-queue execution architecture, replacing the previous scheduling approach. This makes the delivery order of incremental payloads well defined and fixes a class of ordering and lifetime bugs at its root rather than case by case.
• Fixed a hang on a specification-invalid query combining @defer and @stream, where a request could stop producing payloads and never complete.
• Fixed streams whose producers stayed parked on a back-pressured queue and were never released.
• Fixed an invalid-state error that could occur when a sibling @deferred fragment failed.
• Invalid fragment variables now raise a request error instead of failing later.
• Directives are now applied correctly when an SDL document contains both type definitions and type extensions carrying directives.

The security issues have been reported by @BZHunt, who also reviewed the fixes before release. In memory of ZaX, who was the driving force behind this discovery. The first one was also independently found and diagnosed by @bcmyguest.

Thanks to @jkimbo for sponsoring this project.

Release candidate GraphQL-core v3.3.0rc0, based on GraphQL.js v17.0.0rc0.

This release candidate supports Python 3.10 to 3.14.

There are no breaking changes after the last beta version 3.3.0b2.

Notable changes:

• Improved validation of the @defer and @stream directives. The DeferStreamDirectiveOnRootField rule now also forbids these directives on fragments that are spread on abstract types at a mutation or subscription root, and the DeferStreamDirectiveOnValidOperations rule now tracks fragments more thoroughly when detecting @defer/@stream on subscription root selections. As a result, some documents that were previously accepted may now be correctly reported as invalid.

Thanks to @jkimbo for sponsoring this project.

Beta release GraphQL-core v3.3.0b2, based on GraphQL.js v17.0.0b2.

This patch-release supports Python 3.10 to 3.14.

There are no breaking changes after the last beta version 3.3.0b1.

Notable changes:

• GraphQLError now accepts a cause argument and exposes a corresponding cause attribute, adopting the convention of the standard exception cause. When the cause is an exception, it is also exposed via the standard __cause__ attribute. The original_error attribute is now deprecated in favor of cause.
• The following names are now exported from the top-level graphql package: VariableValues, SchemaChange, and the defer/stream validation rules DeferStreamDirectiveLabel, DeferStreamDirectiveOnRootField, DeferStreamDirectiveOnValidOperationsRule, and StreamDirectiveOnListField.

Thanks to @jkimbo for sponsoring this project.

Beta release GraphQL-core v3.3.0b1, based on GraphQL.js v17.0.0b1.

This patch-release supports Python 3.10 to 3.14.

Breaking changes after the last beta version 3.3.0b0:

• subscribe() and Executor no longer accept a per_event_executor argument. The per-event response mapping is now the public module-level function map_source_to_response_event(executor, source_event_stream, root_selection_set_executor=execute_subscription_event) (with a new RootSelectionSetExecutor type alias). To customize per-event subscription execution, compose the pipeline directly: Executor.build() → create_source_event_stream() → map_source_to_response_event(..., root_selection_set_executor=...).

Other notable changes:

• Experimental support for directives on directive definitions (flag-gated): a new experimental_directives_on_directive_definitions parse option, a DirectiveExtensionNode, @deprecated is now allowed on directive definitions, and a new experimental_directive_deprecation introspection option.
• get_introspection_query() gained a configurable type_depth parameter (default 9) controlling the nesting depth of the ofType introspection chain.

Thanks to @jkimbo for sponsoring this project.

Beta release GraphQL-core v3.3.0b0, based on GraphQL.js v17.0.0b0.

This patch-release supports Python 3.10 to 3.14.

Breaking changes after the last alpha version 3.3.0a14:

• Aborted operations now raise the new AbortedGraphQLExecutionError (with the partial result available as aborted_result) instead of the raw abort reason. Aborting during the incremental (defer/stream) phase now also rejects the pending __anext__ with the abort reason instead of yielding a final error payload.
• create_source_event_stream() no longer accepts request args; it now takes the built Executor (call Executor.build() first), or use subscribe() instead.
• subscribe() now raises GraphQLError("Expected subscription operation.") for non-subscription operations.
• execute_query_or_mutation_or_subscription_event() has been renamed to execute_root_selection_set() (and gained a serially argument).
• An explicit Undefined variable value is now treated as omitted, so the variable's default applies (previously coerced to a provided null for nullable variables).
• TypeInfo.get_input_type() and ValidationContext.get_input_type() now return None inside list literals in custom scalar positions; use the new get_parent_input_type() for the enclosing scalar. Variables are now allowed in those positions.

Other notable changes:

• OneOf input coercion is stricter (spec-compliance fixes): unified error messages, and coercion now fails when two fields are provided pre-coercion (e.g. via a missing variable), when unknown fields would mask the field count, or when the single field is only filled in from an invalid default. Unknown fields no longer add a spurious oneOf count error in validation.
• value_from_ast() now rejects unknown input object fields.
• Input coercion fixes: Undefined-valued unknown input object fields are ignored, and an explicit null variable now overrides an input object field's default.
• Better error messages for runtime invalid default values; fragment variables are named as such in execution errors.
• New async_work_finished execution hook on the Executor.
• Incremental delivery robustness: label: null on @defer/@stream means "no label"; fixes for promise rejections, cancellation, and cleanup ordering in async execution.

Thanks to @jkimbo for sponsoring this project.

Alpha release GraphQL-core v3.3.0a14, based on GraphQL.js v17.0.0a14.

This patch-release supports Python 3.10 to 3.14.

This alpha release comes with the following breaking changes:

• ExecutionContext renamed to Executor. The execution context class is now Executor. The old name is not kept as an alias, i.e. from graphql import ExecutionContext no longer works; use from graphql import Executor.
• Custom-executor parameter renamed from execution_context_class to executor_class. Applies to graphql, graphql_sync, execute, execute_sync, experimental_execute_incrementally, subscribe, and create_source_event_stream. The method build_per_event_execution_context is likewise renamed to build_per_event_executor.
• An aborted operation raises the abort reason instead of resolving to a partial error-result.
• A Python int that is too large to represent as a float, or that would lose precision when converted (beyond 2^53), now raises a GraphQLError when coerced to Float (input or output) instead of silently producing an inexact value. Int, ID, String, and Boolean continue to accept Python int as before (and now handle arbitrarily large ints without error).

Thanks to @jkimbo for sponsoring this project.

Alpha release GraphQL-core v3.3.0a13, based on GraphQL.js v17.0.0a9.

This patch-release supports Python 3.10 to 3.14.

Thanks to @jkimbo for sponsoring this project, and to @arichberg, @ckristhoff, @kathychurch and @leszekhanusz for valuable feedback.

Alpha release GraphQL-core v3.3.0a12, based on GraphQL.js v17.0.0a7.

This patch-release supports Python 3.10 to 3.14.

Notable improvements since the last alpha release, in addition to the upstream improvements in v17.0.0.a7:

• Add serialization benchmark (#250)
• Use tuples instead of lists for all AST collection fields (#251)
• De-support Python 3.7 to 3.9 (#252)
• Make visitor immutable friendly (#253)
• Fix parser type safety for stricter AST types (#255)
• Convert AST nodes to frozen dataclasses (#256)
• Support custom async iterables (#258)
• Improve type hints using Self (#259)

Thanks to @jkimbo for sponsoring this project, and to @bellini666, @bigfootjon and @corydolphin for contributing to this release.

Alpha release GraphQL-core v3.3.0a11, based on GraphQL.js v17.0.0a5.

Notable improvements since the last alpha release:

• Python 3.14 is now officially supported
• Enum values, input fields and schemas now keep extensions on sorting (#245)
• Various refactorings and changes concerning @defer and @stream
• Early execution on incremental delivery is now disabled by default
• New recommended validation rule for max introspection depth
• GraphQLEnumType values can now be specified via a callable

Thanks to @jkimbo for sponsoring this project, and to @erikwrede for contributing to this release.

Alpha release GraphQL-core v3.3.0a10, still based on GraphQL.js v17.0.0a3.

Notable improvements since the last alpha release:

• Fixed attribute error on exception with bad source (#240)
• Add @oneOf support to introspection query (#241)
• Use AnyIO instead of pytest-asyncio for running async tests (#242)
• introduced GraphQLWrappedResult to avoid filtering in incremental delivery
• Use uv instead of poetry as default packaging tool
• Some performance improvements and refactorings from upstream
• Various code cleanups

Thanks to @jkimbo for sponsoring this project, and to @agronholm, @erikwrede and @kimjh12 for contributing to this release.

Alpha release GraphQL-core v3.3.0a9, based on GraphQL.js v17.0.0a3.

Notable improvements since the last alpha release:

• Allow nested defers at the same level
• Skip empty subsequent results

Thanks to @patrick91 and @jkimbo for sponsoring this project.

Alpha release GraphQL-core v3.3.0a8, based on GraphQL.js v17.0.0a3.

Notable improvements since the last alpha release:

• Fix IntrospectionQuery type definition (#234)
• Cancel remaining fields on exceptions (#236 and #238)
• Cancel remaining list and iterator items on exceptions
• Cancel remaining type resolvers on exceptions
• Suppress records for deferred fragments that are completely empty
• Add support for @oneOf directives in print_schema

Thanks again to the sponsors of this project, @patrick91, @jkimbo, and to @erikwrede, @magikmark, @mgorven, @sobolevn and @willemt for contributing to this release.

Sorry for lagging behind upstream a bit and not always responding as quickly as I want to.

Alpha release GraphQL-core v3.3.0a7, based on GraphQL.js v17.0.0a3.

Notable improvements since the last alpha release:

• This release also supports Python 3.13
• New incremental response format using id and subPath and pending notifications
• OneOf Input Objects via @oneOf directive
• Speedup sorting and building/extending schema
• Support for fourfold nested lists in introspection
• Transform input objects used as default values (#206)
• Support deep copy of schema with directive with arg of custom type (#210)
• Allow injecting custom data to custom execution context (#226)
• ValidationAbortedError can now be imported (#227)
• Benchmarking with CodSpeed (#230)

Thanks again to the sponsors of this project, @patrick91, @jkimbo, @getsentry, and to @erikwrede, @menma1234, @patrick91, @rafalp and @trim21 for contributing to this release.

Sorry for lagging behind upstream a bit and not always responding as quickly as I want to.

Alpha release GraphQL-core v3.3.0a6, based on GraphQL.js v17.0.0a2.

Changes:

• Support middlewares for subscriptions (#221)
• Introduce new IncrementalPublisher class from GraphQL.js v17.0.0a3

Thanks again to the sponsors of this project, @patrick91, @jkimbo, @codecov and @getsentry, and to @nrbnlulu for contributing to this release.

Alpha release GraphQL-core v3.3.0a5, based on GraphQL.js v17.0.0a2.

This alpha release already includes a lot of the changes and fixes in GraphQL.js v17.0.0a3.

Thanks again to the sponsors of this project, @patrick91, @jkimbo, @sentry and @codecov, and to the contributors for this release, @fedirz and @yilinjuang.

Alpha release GraphQL-core v3.3.0a4, based on GraphQL.js v17.0.0a2.

This alpha release officially supports Python 3.12, and comes with some fixes. It also includes some changes and fixes in GraphQL.js v17.0.0a3.

A big thank you goes to the sponsors of this project, @patrick91, @jkimbo, @sentry and @codecov, and to the contributors for this release, @evanmays and @mrtc0.

Alpha release GraphQL-core v3.3.0a3, based on GraphQL.js v17.0.0a2.

This alpha release ports the remaining changes in GraphQL.js v17.0.0a2.

Particularly noteworthy are these new features:

• Reference implementation of defer and stream spec (graphql/graphql-spec#693)
• Client controlled nullability experiment implementation (graphql/graphql-spec#867)
• Limit max number of tokens in parser (graphql/graphql-js#3684)

There is also one breaking change:

• The subscribe function now stays synchronous when possible. This change aligns the return types of execute and subscribe (as well as the create_source_event_stream function) with respect to returning values or awaitables (graphql/graphql-js#3620).

This alpha release also contains the following changes and features:

• Undefined is not an exception any more (#187)
• Optimized parallel execution when there is only one task (#190)
• GraphQLInputFieldOutType is now importable (#195)
• Include name in representation of nodes (#198)
• Turn MapAsyncIterable into an AsyncGenerator (#199)

Big shoutout to all who are sponsoring me (@Cito), such as @indeedeng, @patrick91 and @jkimbo, and to all who contributed by reporting issues or sending PRs, such as @erikwrede, @ipeterov, @kevinvalk, @kristjanvalur, @LinuxIsCool, @QSHolzner and @rafalp.

Alpha release GraphQL-core v3.3.0a2, still based on GraphQL.js v17.0.0a1.

This alpha release already ports some of the changes in GraphQL.js v17.0.0a2. There will be another alpha release with the remaining changes soon. This alpha release also adds the following new features:

• Solve issues with pickled schemas (#173)
• Use type guards (#183)

Thanks to all who are sponsoring me (@Cito), particularly to Vendia for sponsoring the work on #173, and to others who contributed, particularly to @helderco for the suggestion to use type guards.

Alpha release GraphQL-core v3.3.0a1, based on GraphQL.js v17.0.0a1.

This alpha release ports all of the changes in GraphQL.js v17.0.0a1.

Note that his means the removal of several functions that had been marked as deprecated before.

Other noteable changes:

• starting with this alpha release, Python 3.6 is no longer supported
• we use the new dependency groups feature of poetry (#177)
• support for setuptools has been removed, builds must be done with poetry (#178)
• we now use bugbear and bandit to detect possible security problems and code flaws

Thanks again to all who are sponsoring me (@Cito) and thereby motivated me to continue maintaining this project.

Patch-release GraphQL-core v3.2.13, based on GraphQL.js v16.14.2.

This patch-release supports Python 3.7 to 3.15.

Bug fixes:

• A string escape sequence truncated at the end of the input (e.g. "abc\, "\u, "\u00, or a truncated trailing surrogate) made the lexer raise an unhandled IndexError, which propagated out of parse() and graphql_sync(). It is now reported as a GraphQLSyntaxError with the same message as in GraphQL.js. Thanks to @Hama1cco for reporting this issue.
• On Python 3.14, graphql_sync() and execute_sync() with check_sync=True raised a RuntimeError about a missing event loop instead of reporting that the execution failed to complete synchronously, when called outside of a running event loop.
• assert_abstract_type() now properly reports "abstract type" instead of "composite type" in its error message.
• The type hints for introspection results now use the upper case values for the kind of types that introspection actually returns.

Documentation:

• The API documentation has been extended considerably, following the API docs added in GraphQL.js v16.14.2: all public functions, classes and attributes now have docstrings with documented parameters, return values and examples. The examples are run as doctests, so they are guaranteed to work.
• Added missing public functions and classes to the documentation.

Other changes:

• Added support for Python 3.15.
• Updated development dependencies.

Thanks to @jkimbo for sponsoring this project.

Patch-release GraphQL-core v3.2.12, based on GraphQL.js v16.14.2.

This patch-release supports Python 3.7 to 3.14.

This is a security release. It fixes two denial-of-service vulnerabilities in the validator and the parser. Upgrading is recommended for all users.

Security fixes:

• CVE-2026-75507 (GHSA-vj8h-fx38-h3vc, High) — the OverlappingFieldsCanBeMerged validation rule could be driven into quadratic and worse running time by a small, highly compressible query using repeated inline fragments, occupying a worker for minutes of CPU during validation, before any resolver runs. Validation now enforces a per-document comparison budget and aborts with a GraphQLError once it is exhausted.
• CVE-2026-75508 (GHSA-r77w-qph3-7vf8, High) — comment tokens were allocated and retained but not counted toward the parser's max_tokens limit, so a comment-padded document could bypass the limit while allocating one token object per comment. max_tokens now counts every token the parser consumes, including skipped comments.

Please note the two behaviour changes this implies:

• A pathological query that previously validated — slowly — now produces a validation error. Realistic queries stay far below the limit, which defaults to 250,000 field comparisons and can be adjusted by assigning to graphql.validation.rules.overlapping_fields_can_be_merged.MAX_FIELD_COMPARISONS.
• Comments now count toward max_tokens, so a comment-heavy document that was previously accepted may now be rejected. If you parse documents with substantial comments and set max_tokens, you may need to raise the limit. The token_count of a parsed document now includes comments as well.

Both limits complement, but do not replace, a request body-size limit applied to the decompressed request body in your web framework.

Other changes:

• Updated development dependencies and CI tooling.

The security issues were reported by @BZHunt, who also reviewed the fixes before release. In memory of ZaX, who was the driving force behind this discovery. The first one was also independently found and diagnosed by @bcmyguest.

Thanks to @jkimbo for sponsoring this project.

Patch-release GraphQL-core v3.2.11, based on GraphQL.js v16.14.1.

This patch-release supports Python 3.7 to 3.14.

Notable changes:

• Allow configuration of the ofType introspection depth
• Add support for directives on directive definitions
• Restore variable own-property checks in value_from_ast
• Remove unused variable-definition tracking in ValuesOfCorrectTypeRule

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.10, based on GraphQL.js v16.13.0.

This patch-release supports Python 3.7 to 3.14.

New features:

• Add support for schema coordinates (parsing and resolving)
• Support descriptions on executable definitions (e.g. variable definitions)
• Add a max_coercion_errors option

Bug fixes:

• Fix incorrect validation errors when variable descriptions are used
• Don't add sibling errors after null propagation has occurred
• Remove erroneous oneOf validation from the "values of correct type" rule
• Validate that nullable variables aren't passed to oneOf input object fields (per spec)
• Catch unhandled exceptions during abstract type resolution

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.9, based on GraphQL.js v16.10.0.

This patch-release supports Python 3.7 to 3.14.

Notable changes:

• Fix OverlappingFieldsCanBeMergedRule to catch field-merge conflicts hidden behind nested fragments
• Fix handling of empty selection sets
• Correctly type extensions in GraphQLFormattedError
• Add kind to the introspection query/mutation/subscription root types
• Expose token_count on DocumentNode
• Preserve schema and input-field properties (e.g. descriptions) when sorting

Thanks to @kathychurch and @arichberg for reporting the sorting issue.

Also thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.8, based on GraphQL.js v16.9.0.

This patch-release supports Python 3.7 to 3.14.

One change has been backported from the v3.3 branch:

• Require non-empty directive locations

Also, for backward compatibility, introspection.TypeResolvers is available again, as alias for TypeFields.

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.7, based on GraphQL.js v16.9.0.

This patch-release supports Python 3.7 to 3.14.

The following changes have been backported from the v3.3 branch:

• Keep extensions when sorting schemas
• Introduce "recommended" validation rules
• Implement OneOf Input Objects via @oneOf directive
• Values can now be passed to GraphQLEnumType as a thunk
• Solved issues with pickled schemas

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.6, based on GraphQL.js v16.8.2.

This patch-release supports Python 3.6 to 3.13. Notable fixes:

• Transform input objects used as default values (#206)
• Allow deep copy of schema with directive with args of custom type (#210)

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.5, based on GraphQL.js v16.8.2.

This patch-release supports Python 3.6 to 3.13.

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.4, based on GraphQL.js v16.8.2.

This patch-release supports Python 3.6 to 3.12 and includes these changes:

• Fix invalid original_error propagation in custom scalars
• Fix performance degradation in OverlappingFieldsCanBeMergedRule
• Support fourfold nested lists in introspection
• Avoid various deprecation warnings with newer Python versions

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.3, based on GraphQL.js v16.6.0.

This patch-release includes only one change in GraphQL.js v16.6.0:

• The parser now allows to limit the number of tokens

Thanks to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.2, based on GraphQL.js v16.4.0.

This patch-releases includes the changes in GraphQL.js v16.4.0, and the following fixes:

• Require typing extensions when needed
• Recommend using poetry instead of pipenv in the docs (#161)
• Cast error message to string to handle proxy objects (#175)
• Remove newline in description (#180)

Thanks to @chenrui333, @conao3, @jkimbo, @singingwolfboy for contributing and to all who are sponsoring me (@Cito) for maintaining this project.

Patch-release GraphQL-core v3.2.1, based on GraphQL.js v16.3.0.

This patch-releases includes the changes in GraphQL.js v16.3.0, and the following fix:

• Serialize with maximum precision when converting float to FloatValue (#164)

Thanks to @bennyweise for contributing and all who are sponsoring me (@Cito) for maintaining this project.

Final release of GraphQL-core v3.2.0, based on GraphQL.js v16.2.0.

See v3.2.0rc1, v3.2.0rc2, v3.2.0rc3, v3.2.0rc4, v3.2.0rc5 and the changelog of GraphQL.js for a complete list of changes.

Thanks to all who contributed and are sponsoring me (@Cito) for maintaining this project.

Pre-release GraphQL-core v3.2.0rc5, based on GraphQL.js v16.1.0.

In addition to porting the recent changes in GraphQL.js, this pre-release also contains the following improvements:

• Add flag for using enum names or members as values (#73)
• Add typed dicts for to_kwargs results (#99)
• Add ast_to_dict utility function (#136)
• Make print_block_string work with string proxy objects (#153)
• Prevent infinite loop in OverlappingFieldsCanBeMergedRule (fetched ahead)

Please test this pre-release and report any issues, the final release is imminent.

Pre-release GraphQL-core v3.2.0rc4, based on GraphQL.js v16.0.1.

In addition to porting the recent changes in GraphQL.js, this pre-release also contains the following improvements:

• Use typed dictionaries for introspection results (#99)
• Deprecate FrozenDict/List, use tuples as node lists (#112)
• Experimental support for async iterables as list values (#123)
• Make print_block_string work with string proxy objects (#153)

Note that the use of tuples may break code that tries to modify the AST.

Please test this pre-release and report any issues, the final release is imminent.

Pre-release GraphQL-core v3.2.0rc3, based on GraphQL.js v16.0.0rc3.

In addition to porting the recent changes in GraphQL.js, this pre-release also contains the following improvements:

• Add sync and async execution benchmarks (#141)
• Minor code simplifications (#146)
• Optimize node hash method through caching (#150)
• Optimize performance of character class predicates
• Include Python 3.10 in default test matrix

Pre-release GraphQL-core v3.2.0rc2, based on GraphQL.js v16.0.0rc2.

• Make thunk resolver simpler and backward compatible

Pre-release GraphQL-core v3.2.0rc1, based on GraphQL.js v16.0.0rc2.

In addition to porting the recent changes in GraphQL.js, this pre-release also contains the following improvements:

• Set enum value values to value names in build_client_schema (#138)
• Fix camel to snake case conversion with digits (#140)
• Support Python 3.10

Patch release GraphQL-core v3.1.7, based on GraphQL.js v15.8.0.

This release includes minor changes and improvements, in particular:

• Set enum value values to value names in build_client_schema (#138)
• Fix camel to snake case conversion with digits (#140)
• Preserve deprecation_reason on GraphQLInputFields (d1ffaef2ec3e5e475cb8ae52397489fd05ea6a12)
• Add missing __Directive.args(includeDeprecated) (0df0a32fe9cae2edafdd985f099490b55dca13e2)
• Fix original_error.extensions overriding extensions argument (810d712ca53e5356027e6930b9585cf56152d3f5)

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

This release includes only some minor changes and improvements.

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.

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.

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.

Patch release GraphQL-core v3.1.2, based on GraphQL.js v15.1.0.

This release includes the following improvements:

• Added @specifiedBy directive
• Extended type definitions (#89)
• Enum type for visitor return values (#96)
• Visitors can now use class and static methods
• Lists in AST nodes are not optional any more (#98)

Thanks to everyone who helped with their feedback.

Bugfix release GraphQL-core v3.1.1, based on GraphQL.js v15.0.0.

The following issues are fixed in this release:

• Fixed rendering of ReST in docstring (#84, #85, #86, #87)
• Added type hint to default_field_resolver (#88)
• Fixed memoization of collect_subfields (#91)
• Fixed method name in Visitor docstring (#92)

Contributors to this release were:

@Cito, @hoefling, @nawatts, @rafalp

Thanks to everyone who helped by sending bug reports or pull requests.

Final release of GraphQL-core v3.1.0, based on GraphQL.js v15.0.0.

See the three pre-releases v3.1.0b0, v3.1.0b1 and v3.1.0b2 for a complete list of changes.

Third beta release of GraphQL-core 3.1, based on GraphQL.js v15.0.0rc2.

In addition to incorporating the latest changes from the master branch of GraphQL.js, this release also contains the following improvements:

• Increased performance by using a faster isawaitable() function (#54).
• Nodes and some other objects are now extensible and weak-referencable (#82).

We also renamed the repository on GitHub from graphql-python/graphql-core-next to graphql-python/graphql-core.

Contributors to this release were:

@Cito, @astronouth7303, @Hellzed and @qeternity

Thanks to everybody who contributed by sending bug reports or pull requests. Please continue to report any problems you find in this beta release, so that these can be fixed in the final v3.1 release.

Second beta release of GraphQL-core 3.1, based on GraphQL.js v15.0.0rc2.

In addition to incorporating the latest changes in GraphQL.js v15.0.0rc2, this release also contains the following improvements and changes:

• Following a change in GraphQL.js to keep the order of user provided types, the type map reducer for the GraphQLSchema has been removed.
• We now support inheritance when evaluating the __typename attribute (#25).
• FieldNodes and InputValueNodes are now only DefinitionNodes, not TypeDefinitionNodes.
• The test suite now has 100% coverage, and less coverage will count as failure.

Contributors to this release were:

@Cito, @Hellzed

Thanks to everybody who contributed by sending bug reports or pull requests. Please continue to report any problems you find in this beta release, so that these can be fixed in the final v3.1 release.

First beta release of GraphQL-core 3.1, based on GraphQL.js v15.0.0rc1.

In addition to incorporating the latest changes from GraphQL.js (see the list of changes in GraphQL.js v15.0.0a1, v15.0.0a2 and v15.0.0rc1), this release also contains the following improvements and changes:

• Change: Use Undefined instead of INVALID which is now deprecated (#77)
• Use explicit Optional type on arguments (#76)
• Remove unnecessary result type annotation from __init__ methods (python/mypy#5677)
• Better docstring for ast_from_value
• Better docstring for lexicographic_sort_schema (#75)
• Fixed a minor issue when coverting lists in ast_from_value()
• Fixed a minor issue with MapAsyncIterator.athrow()
• Improved test coverage (trying to reach 100% for final release)

Contributors to this release were:

@Cito, @hoefling

Thanks to everybody who contributed by sending bug reports or pull requests. Please continue to report any problems you find in this beta release, so that these can be fixed in the final v3.1 release.

Patch release GraphQL-core v3.0.6, based on GraphQL.js v14.7.0.

This release backports Python 3.9 and 3.10 support to the 3.0 branch.

Bugfix release GraphQL-core v3.0.5, based on GraphQL.js v14.6.0.

The following issues are fixed in this release:

• Added type hint to default_field_resolver (#88)
• Fixed memoization of collect_subfields (#91)
• Fixed method name in Visitor docstring (#92)

Contributors to this release were:

@Cito, @hoefling, @nawatts, @rafalp

Thanks to everyone who helped by sending bug reports or pull requests.

Patch release of GraphQL-core 3, based on GraphQL.js v14.6.0.

The primary fix is the new repository address github.com/graphql-python/graphql-core in the meta data.

Patch release of GraphQL-core 3, based on GraphQL.js v14.6.0.

This is essentially the same as version 3.0.2 except for one minor change:

• Added Undefined as a forward compatible alias for INVALID, which should be imported from the top level.

Patch release of GraphQL-core 3, based on GraphQL.js v14.6.0.

This is essentially the same as version 3.0.1 except for one minor change:

• Added the missing validation rules that could not be imported from the graphql and graphql.validation packages.

Some requirements have also been updated, and we officially support Python 3.8 now.

Patch release of GraphQL-core 3, based on GraphQL.js v14.5.8.

This is essentially the same as version 3.0.0 except for one minor change:

• The utilities.get_introspection_query module has been renamed back to utilities.introspection_query, since that was the name used in GraphQL.js v14.5.8 - renaming the module will be postponed to a version that replicates GraphQL.js v15.0.0.

Note that the introspection_query constant was already deprecated in v14 and had not been ported to graphql-core, like some other deprecated features.

Final release of GraphQL-core 3, based on GraphQL.js v14.5.8.

GraphQL-core 3 is the successor to both GraphQL-core 2 and GraphQL-core-next.

In addition to porting the minor changes in GraphQL.js since v14.5.6, this release also contains the following improvements:

• GraphQL-core 3 now officially supports Python 3.8
• Use mypy 0.750 and the new semantic analyzer (#67)
• Fix for possible sort errors in build_response() (#68)
• Document the differences between GraphQL-core 3 and GraphQL.js (#24)

See also the changes in v3.0.0b0 and v3.0.0b1.

Contributors to this release were:

@Cito, @tebanep

Thanks to everyone who sent bug reports or pull requests.

Second beta release of GraphQL-core 3, based on GraphQL.js v14.5.6.

GraphQL-core 3 is the successor to both GraphQL-core 2 and GraphQL-core-next.

In addition to incorporating the latest changes from GraphQL.js (see particularly the list of changes in GraphQL.js v14.5.5), this release also contains the following improvements and changes:

• Changes: format_error now returns locations as a list of dicts (#62)
• Bugs: Detect args passed to directive without args (#63)

Contributors to this release were:

@Cito, @Dodobibi, @ktosiek

Thanks to everybody who contributed by sending bug reports or pull requests. Please continue to report any problems you find in this beta release, so that these can be fixed in the final v3 release.

First beta release of GraphQL-core 3, based on GraphQL.js v14.5.0.

GraphQL-core 3 is the successor to both GraphQL-core 2 and GraphQL-core-next.

In addition to incorporating the latest changes from GraphQL.js (see particularly the list of changes in GraphQL.js v14.5.0), this release also contains the following improvements and changes:

• Features: Support using lazy descriptions for GraphQL types (#58)
• Performance: Add pytest-benchmark and port the benchmarks from GraphQL.js (#55)
• Performance: Use identity instead of hash for caching subfields in collect_subfields (#56)
• Changes: Use FrozenLists in AST nodes (#45)
• Changes: Changed is_nullish() to make it play nice with numpy arrays (#60)
• Bugs: Fixed issue #43 with getting parse_literal via to_kwargs()
• Bugs: Fix hash method for AST nodes (#45)
• Docs: Fix typo in docs for using SDL (#48)
• Docs: Update installation instructions (#50)
• Docs: Run all code snippets as part of the test suite
• Polish: Run type check also for functions without type annotations

Contributors to this release were:

@Cito, @CorrosiveKid, @delyanr, @ktosiek, @mvanlonden, @qqi0O0, @thomascobb

Thanks to everybody who contributed by sending bug reports or pull requests. Please continue to report any problems you find in this beta release, so that these can be fixed in the final v3 release.