[dependabot]

Bumps graphql-core from 3.2.3 to 3.3.0.

Release notes

Sourced from graphql-core's releases.

v3.3.0

Stable release GraphQL-core v3.3.0, based on GraphQL.js v17.0.2.

This release supports Python 3.10 to 3.15.

This is the first stable release of GraphQL-core 3.3, which follows GraphQL.js 17. Since the minor version of GraphQL-core corresponds to the major version of GraphQL.js, this release contains breaking changes compared to GraphQL-core 3.2. Most of them come from GraphQL.js 17 and are described in the GraphQL.js v16 to v17 upgrade guide. If you need to stay compatible with GraphQL.js 16 or need support for Python 3.7 to 3.9, you can continue to use GraphQL-core 3.2.13.

Breaking changes compared to GraphQL-core 3.2.13:

• Python 3.7 to 3.9 are no longer supported.
• Functions and options that had been deprecated in GraphQL.js 16 have been removed.
• AST nodes are now frozen dataclasses, and all AST collection fields are tuples instead of lists.
• ExecutionContext has been renamed to Executor, and the parameter execution_context_class to executor_class.
• subscribe() stays synchronous when possible, like execute(), and raises a GraphQLError for non-subscription operations. create_source_event_stream() now takes a built Executor (see Executor.build()) instead of the request arguments.
• A Python int that cannot be represented exactly as a float now raises a GraphQLError when coerced to Float.
• An explicit Undefined variable value is treated as omitted, so the variable's default applies.
• Input coercion follows the specification more strictly, and default values are validated against their types.
• Directives on directive definitions and directive extensions are now part of the language, so the parser option experimental_directives_on_directive_definitions has been removed.
• Input objects that cannot be given a finite value are rejected by schema validation, with a new error message for circular input object references.
• TypeInfo.get_input_type() and ValidationContext.get_input_type() return None inside list literals in custom scalar positions; use the new get_parent_input_type() for the enclosing scalar.

New features compared to GraphQL-core 3.2.13:

• Incremental delivery with @defer and @stream via experimental_execute_incrementally(), following the current spec proposal.
• Experimental fragment arguments (parser option experimental_fragment_arguments).
• Operations can be aborted with an AbortSignal, raising an AbortedGraphQLExecutionError with the partial result, and executors support hooks.
• The new function find_schema_changes() also reports safe changes, in addition to breaking and dangerous changes.
• The API documentation has been updated to GraphQL.js 17; all examples in the docstrings are run as doctests.

Thanks to @​jkimbo for sponsoring this project, to @​Hama1cco for reporting a bug in the lexer, and to everybody who tested the pre-releases and reported issues.

v3.3.0rc1

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.

... (truncated)

Commits

• 894141f Bump version
• ef9b7e2 Update README for the stable release 3.3.0
• c0b19ae Use simulation mode for CodSpeed benchmarks
• 9f51841 docs: further improve general execution docs
• 996cdae fix: detect default-value changes on input object fields
• fac0e60 fix(map_schema_config): fix context for schema argument mapper
• a4f31e3 feat: graduate directives on directives
• a4b3f9c fix(KnownDirectivesRule): directive locations for input obj extensions
• 9f566c1 OneOf Inhabitability
• 9e93687 Remove incremental key from the formatted initial incremental result
• Additional commits viewable 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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]

Labels

The following labels could not be found: kind/dependencies, sdk/python. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 7 days with no activity.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.