Repository navigation
chore(deps): update dependency @graphql-tools/schema to v10.1.5 - #49
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
January 23, 2025 17:58
62fabee to
e356a43
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
February 9, 2025 13:04
e356a43 to
d28b4ed
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
February 11, 2025 11:02
d28b4ed to
7d82787
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
February 21, 2025 15:15
7d82787 to
70145a3
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
3 times, most recently
from
March 4, 2025 01:58
e581253 to
a9e00cb
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
March 11, 2025 13:30
a9e00cb to
dd6dad5
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
3 times, most recently
from
March 14, 2025 03:00
a1e9adb to
fd5fbc0
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
August 13, 2025 17:05
9b4c5b6 to
bf6f1ac
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
September 25, 2025 21:30
bf6f1ac to
4ca019f
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
October 21, 2025 18:06
4ca019f to
74fc54b
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
October 30, 2025 16:55
74fc54b to
5966091
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
November 4, 2025 20:50
5966091 to
9ee127b
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
November 12, 2025 01:41
6b43dbb to
82abd51
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
November 12, 2025 11:15
82abd51 to
847c520
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
November 19, 2025 00:28
847c520 to
d916f0d
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
November 28, 2025 10:52
d916f0d to
692d425
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
December 3, 2025 18:13
692d425 to
2877261
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
January 7, 2026 05:52
047dc49 to
e202245
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
January 8, 2026 17:28
e202245 to
4989ac4
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
January 19, 2026 15:14
4989ac4 to
25dbd54
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
February 2, 2026 20:35
25dbd54 to
ab92d3d
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
March 5, 2026 14:40
ab92d3d to
15a45c5
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
March 14, 2026 12:56
15a45c5 to
249cfca
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
March 27, 2026 17:44
7180fd2 to
c7f1e92
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
10.0.2→10.1.5Release Notes
ardatan/graphql-tools (@graphql-tools/schema)
v10.1.5Compare Source
Patch Changes
#8445
82457d1Thanks @ardatan! - dependencies updates:@graphql-tools/merge@^9.2.7↗︎ (from^9.2.6, independencies)@graphql-tools/utils@^12.0.4↗︎ (from^12.0.3, independencies)#8445
82457d1Thanks @ardatan! - Fix: Preserve symbol-keyed GraphQL extensions when building, merging, or extracting schemas.GraphQL.js v17 allows
string | symbolkeys on schema/type/fieldextensions(viatoObjMapWithSymbols).@graphql-toolswas dropping those symbol keys in two places:mergeDeeponly walked enumerable string keys (for...in), so symbol extensions were lost when applyingschemaExtensions.extractExtensionsFromSchemadid not copy non-enumerable own symbol keys (enumerable symbols already survive object rest/spread; the explicit loop covers the non-enumerable case).Example (bug)
Schema extension merge/extract and resolver merging always enable
{ enumerable: true, nonEnumerable: true }so symbol keys survive in tools' own merge/extract paths on every supported GraphQL.js major. (GraphQL.js itself may still drop symbol keys from field configs below v17 when rebuilding types.)mergeDeepAPImergeDeepnow accepts an options object. The old positional boolean arguments still work but are deprecated.respectSymbolsdefaults to{ enumerable: false, nonEnumerable: false }(symbols dropped), matching the historical default. The legacy 5th positional flag still maps to{ nonEnumerable: true }only.Resolver map types (
IResolvers/ field resolverextensionsand type__extensions) now useExtensionsObject(Record<string | symbol, any>), so symbol-keyed resolver extensions type-check under GraphQL.js v17+.82457d1,98673c3,a75d725,82457d1]:v10.1.4Compare Source
Patch Changes
fd95dc9]:v10.1.3Compare Source
Patch Changes
19f5b33]:v10.1.2Compare Source
Patch Changes
b1fbba2,20d36a5]:v10.1.1Compare Source
Patch Changes
2262087,5523c4b,60db079,57e316d,1c1c5a0,1c1c5a0,0b9529f]:v10.1.0Compare Source
Minor Changes
#8346
2273c21Thanks @ardatan! - This release adds GraphQL v17 support and aligns
the existing executor implementation with the latest GraphQL v17 API changes. The following
changes are included:
getAsyncHelpersis now available onGraphQLResolveInfo. Itstrackmethod is used wheneverwaitUntilis available, as in Yoga'sExplicit Resource Management
getAbortSignalis now available onGraphQLResolveInfo, matching behavior that was alreadyavailable in this executor implementation, as in Yoga's
Execution Cancellation
GraphQLResolveInfoautomatically alignsvariableValuesaccording to the GraphQL version forbetter compatibility. In GraphQL v17 and above,
variableValuesfollows the wrapped shape(
{ coerced, sources }) expected by GraphQL APIs. In GraphQL v16 and below,variableValuesremains a flat map as in previous versions.
__serializeand__parseValue, they are automaticallymapped to
coerceOutputValueandcoerceInputValuein GraphQL v17.@graphql-tools/executor'sgetVariableValuesnow returns{ variableValues }on success, where
variableValuesis aVariableValuesobject ({ coerced, sources }). Onfailure, it returns
{ errors }.collectFields,shouldIncludeNode,getDeferValues, andcollectSubFieldsnowneed a
VariableValuesobject instead ofRecord<string, any>for thevariableValuesargument.
visitResultnow internally normalizesExecutionRequest.variablesinto aVariableValues-compatible shape ({ coerced, sources }) before traversing selections.Patch Changes
[
2273c21,7fe0319]:v10.0.38Compare Source
Patch Changes
[
e90719b]:v10.0.37Compare Source
Patch Changes
[
615c1a2]:v10.0.36Compare Source
Patch Changes
[
79f1998]:v10.0.35Compare Source
Patch Changes
[
2609c94]:v10.0.34Compare Source
Patch Changes
[
981d461]:v10.0.33Compare Source
Patch Changes
[
a4b7dce]:v10.0.32Compare Source
Patch Changes
[
ae36a0e]:v10.0.31Compare Source
Patch Changes
[
6f3776c]:v10.0.30Compare Source
Patch Changes
[
2118a80]:v10.0.29Compare Source
Patch Changes
[
2fe123a]:v10.0.28Compare Source
Patch Changes
[
dddc5f6]:v10.0.27Compare Source
Patch Changes
[
fbb58b5]:v10.0.26Compare Source
Patch Changes
[
fd105f4,fded91e,3b99a9b]:v10.0.25Compare Source
Patch Changes
[
984d542,984d542,32d0457]:v10.0.24Compare Source
Patch Changes
[
e5f98c2,3c21496,e5f98c2,22af985,53db005]:v10.0.23Compare Source
Patch Changes
[
d123e26]:v10.0.22Compare Source
Patch Changes
[
4899c62,90a717e,26518de]:v10.0.21Compare Source
Patch Changes
[
155944b]:v10.0.20Compare Source
Patch Changes
[
4a2eb14]:v10.0.19Compare Source
Patch Changes
[
3547bba]:v10.0.18Compare Source
Patch Changes
[
651a5dc]:v10.0.17Compare Source
Patch Changes
357b2eeThanks @renovate! - dependencies updates:
value-or-promise@^1.0.12↗︎ (fromdependencies)[
0a3e193,357b2ee]:v10.0.16Compare Source
Patch Changes
[
53bb601,53bb601]:v10.0.15Compare Source
Patch Changes
[
4912f19]:v10.0.14Compare Source
Patch Changes
[
2c70d27]:v10.0.13Compare Source
Patch Changes
[
6a8123b]:v10.0.12Compare Source
Patch Changes
020b9e4Thanks @ardatan! - `AbortSignal` in `GraphQLResolveInfo`, and
`AbortSignal` in `ExecutionRequest`
Updated dependencies
[
020b9e4]:v10.0.11Compare Source
Patch Changes
696a0d5Thanks @renovate! - dependencies updates:
@graphql-tools/merge@^9.0.11↗︎(from
^9.0.10, independencies)@graphql-tools/utils@^10.6.1↗︎(from
^10.6.0, independencies)[
696a0d5,1b24656]:v10.0.10Compare Source
Patch Changes
[
1e02935]:v10.0.9Compare Source
Patch Changes
[
414e404]:v10.0.8Compare Source
Patch Changes
[
dc5043b]:v10.0.7Compare Source
Patch Changes
[
cf2ce5e]:v10.0.6Compare Source
Patch Changes
0286437Thanks @ardatan! - Improve directive extraction
Updated dependencies
[
0286437]:v10.0.5Compare Source
Patch Changes
b8bf584Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
directive handling in the extensions
Updated dependencies
[
b8bf584]:v10.0.4Compare Source
Patch Changes
#6194
7368829Thanks @ardatan! - Handle interface objects in a different way
Updated dependencies
[
7368829,e10c13a]:v10.0.3Compare Source
Patch Changes
[
e90719b]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.