fix(deps): update graphql-tools monorepo - #4049
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
3 times, most recently
from
July 12, 2026 18:05
3909cc3 to
8d1663b
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
4 times, most recently
from
July 21, 2026 03:15
6937333 to
036a718
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
July 24, 2026 16:32
036a718 to
5b6163f
Compare
renovate
Bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
July 30, 2026 17:05
5b6163f to
5d0b190
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
1 participant
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:
9.1.9→9.2.210.0.33→10.0.3811.1.0→11.2.2Release Notes
ardatan/graphql-tools (@graphql-tools/merge)
v9.2.2Compare Source
Patch Changes
[
e90719b]:v9.2.1Compare Source
Patch Changes
[
615c1a2]:v9.2.0Compare Source
Minor Changes
79f1998Thanks @eddeee888! - Support graphql@17
v9.1.11Compare Source
Patch Changes
[
2609c94]:v9.1.10Compare Source
Patch Changes
[
981d461]:ardatan/graphql-tools (@graphql-tools/schema)
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]:ardatan/graphql-tools (@graphql-tools/utils)
v11.2.2Compare Source
Patch Changes
e90719bThanks @pbomb! - fix mergeDeep to treat explicit undefined property
values as overrides rather than skipping them, distinct from an absent property
v11.2.1Compare Source
Patch Changes
615c1a2Thanks @pbomb! - fix mergeDeep to treat null property values as
explicit overrides rather than skipping them
v11.2.0Compare Source
Minor Changes
2609c94Thanks @eddeee888! - getDocumentNodeFromSchema: Add arg
defaultValue support for graphql@17
v11.1.1Compare Source
Patch Changes
#8256
981d461Thanks @twavv! - Fix
mergeDeepreturningundefinedinstead of{}when merging two or more empty objects.
Previously the output accumulator was only initialized inside the per-key loop, so merging sources
with no own keys (e.g.
mergeDeep([{}, {}])) left itundefined. This silently droppedempty-object values during nested merges (
{ data: {} }became{ data: undefined }), whichcould surface as "Cannot return null for non-nullable field" errors when stitching schemas. The
accumulator is now initialized as soon as an object source is encountered.
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.