fix(deps): update dependency @graphql-tools/utils to v12

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-tools/utils (source)	^11.2.0 → ^12.0.0

---

Release Notes

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

v12.0.0

Compare Source

Major Changes

• #​8346
  2273c21
  Thanks @​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:

  • getAsyncHelpers is now available on GraphQLResolveInfo. Its track method is used whenever
    waitUntil is available, as in Yoga's
    Explicit Resource Management
  • getAbortSignal is now available on GraphQLResolveInfo, matching behavior that was already
    available in this executor implementation, as in Yoga's
    Execution Cancellation
  • GraphQLResolveInfo automatically aligns variableValues according to the GraphQL version for
    better compatibility. In GraphQL v17 and above, variableValues follows the wrapped shape
    ({ coerced, sources }) expected by GraphQL APIs. In GraphQL v16 and below, variableValues
    remains a flat map as in previous versions.
  • If your custom scalar resolvers define __serialize and __parseValue, they are automatically
    mapped to coerceOutputValue and coerceInputValue in GraphQL v17.
  • BREAKING: @graphql-tools/executor's getVariableValues now returns { variableValues }
    on success, where variableValues is a VariableValues object ({ coerced, sources }). On
    failure, it returns { errors }.
  • BREAKING: collectFields, shouldIncludeNode, getDeferValues, and collectSubFields now
    need a VariableValues object instead of Record<string, any> for the variableValues
    argument.
  • visitResult now internally normalizes ExecutionRequest.variables into a
    VariableValues-compatible shape ({ coerced, sources }) before traversing selections.

v11.2.2

Compare Source

Patch Changes

• #​8302
  e90719b
  Thanks @​pbomb! - fix mergeDeep to treat explicit undefined property
  values as overrides rather than skipping them, distinct from an absent property

v11.2.1

Compare Source

Patch Changes

• #​8204
  615c1a2
  Thanks @​pbomb! - fix mergeDeep to treat null property values as
  explicit overrides rather than skipping them

---

Configuration

📅 Schedule: (UTC)

• 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 becomes conflicted, 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.