fix(deps): update dependency @graphql-tools/utils to v10.5.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-tools/utils (source)	10.1.2 -> 10.5.6

---

Release Notes

ardatan/graphql-tools (@​graphql-tools/utils)

v10.5.6

Compare Source

Patch Changes

• #​6677
  dc5043b
  Thanks @​enisdenjo! - onError and onEnd callbacks from
  mapAsyncIterator are invoked only once regardless of how many times throw/return was called
  on the iterator

v10.5.5

Compare Source

Patch Changes

• #​6524
  cf2ce5e
  Thanks @​kachkaev! - Make two types compatible with strict tsc
  config

v10.5.4

Compare Source

Patch Changes

• 0286437
  Thanks @​ardatan! - Improve directive extraction

v10.5.3

Compare Source

Patch Changes

• 2124d7d
  Thanks @​ardatan! - Allow invalid path in `getDirectiveExtensions`

v10.5.2

Compare Source

Patch Changes

• 07b87ed
  Thanks @​ardatan! - Respect extensionASTNodes in directable
  GraphQLSchema object

v10.5.1

Compare Source

Patch Changes

• 6291e14
  Thanks @​ardatan! - Add all args from extensions to the AST even if
  they don't exist in the directive def

v10.5.0

Compare Source

Minor Changes

• 8fd7703
  Thanks @​ardatan! - Export getDirectiveExtensions

v10.4.0

Compare Source

Minor Changes

• b8bf584
  Thanks @​ardatan! - Introduce `getDirectiveExtensions` and refactor
  directive handling in the extensions

v10.3.4

Compare Source

Patch Changes

• #​6420
  a867bbc
  Thanks @​ardatan! - mapAsyncIterator now accepts AsyncIterable

v10.3.3

Compare Source

Patch Changes

• #​6385
  d0f7d75
  Thanks @​tobiasdiez! - remove generic package export

• Updated dependencies
  [d0f7d75]:

  • [email protected]

v10.3.2

Compare Source

Patch Changes

• a276ba8
  Thanks @​ardatan! - Respect directive extensions on `pruneSchema`

v10.3.1

Compare Source

Patch Changes

• #​6325
  9792e80
  Thanks @​ardatan! - Make the executor disposable optional

v10.3.0

Compare Source

Minor Changes

• #​6323
  cacf20f
  Thanks @​ardatan! - Implement Symbol.dispose or Symbol.asyncDispose
  to make `Executor`s `Disposable`

v10.2.3

Compare Source

Patch Changes

• #​6278
  66c99d9
  Thanks @​ardatan! - Handle @defer

v10.2.2

Compare Source

Patch Changes

• #​6238
  0f7059b
  Thanks @​ardatan! - If the given objects are arrays with the same
  length, merge the elements.

  const a = [{ a: 1 }, { b: 2 }]
  const b = [{ c: 3 }, { d: 4 }]
  const result = mergeDeep(a, b) // [{ a: 1, c: 3 }, { b: 2, d: 4 }]

v10.2.1

Compare Source

Patch Changes

• #​6194
  7368829
  Thanks @​ardatan! - Handle interface objects in a different way

• #​6188
  e10c13a
  Thanks @​ardatan! - Add respectArrayLength flag to mergeDeep so
  instead of concatenating the arrays, elements of them will be merged if they have the same length

v10.2.0

Compare Source

Minor Changes

• #​6105 5567347 Thanks @​ardatan! - Add enumValueFilter and directiveFilter to filterSchema

Patch Changes

• #​6105 5567347 Thanks @​ardatan! - Handle fields in unmerged types as both isolated and non-isolated fields

v10.1.3

Compare Source

Patch Changes

• #​6055 4093f70 Thanks @​enisdenjo! - Disallow new lines in paths when checking with isValidPath

  A string may sometimes look like a path but is not (like an SDL of a simple
  GraphQL schema). To make sure we don't yield false-positives in such cases,
  we disallow new lines in paths (even though most Unix systems support new
  lines in file names).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2d5bbe1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR