chore(deps): bump @graphql-tools/utils and @graphql-tools/merge

[dependabot]

Bumps @graphql-tools/utils to 12.0.3 and updates ancestor dependency @graphql-tools/merge. These dependencies need to be updated together.

Updates @graphql-tools/utils from 9.2.1 to 12.0.3

Changelog

Sourced from @​graphql-tools/utils's changelog.

12.0.3

Patch Changes

• #8482 19f5b33 Thanks @​ardatan! - Compare incremental path keys to __proto__ at the property access in setObjectKeyPath, in addition to the existing isSafeObjectKey check.

12.0.2

Patch Changes

• #8456 b1fbba2 Thanks @​renovate! - dependencies updates:

  • Updated dependency @whatwg-node/promise-helpers@^2.0.0 ↗︎ (from ^1.0.0, in dependencies)

• #8467 20d36a5 Thanks @​ardatan! - Fix prototype pollution in mergeIncrementalResult

  Path segments are now rejected unless they are primitive strings or numbers, and keys named __proto__, constructor or prototype are still blocked. Previously a non-primitive segment such as ["__proto__"] bypassed the string equality guard and was coerced into a write on Object.prototype.

  Also exports shared isSafeObjectKey / isDangerousObjectKey helpers used by this path walker and other package call sites. @graphql-tools/merge and @graphql-tools/mock are patched so they ship with the new imports; updateInternalDependencies raises their utils floor when 12.0.2 is versioned.

12.0.1

Patch Changes

• #8368 60db079 Thanks @​ardatan! - Omit mutation/subscription from printSchemaWithDirectives when those root types are no longer present on the schema (e.g. after pruneSchema).

• #8366 57e316d Thanks @​ardatan! - Allow % in paths checked by isValidPath (e.g. directories from URL-encoded repo names).

• #8370 1c1c5a0 Thanks @​ardatan! - Clean up observableToAsyncIterable queues and unsubscribe when the observable completes, so iterators do not retain references after done. Fixes leak detection flakes related to #8057.

• #8370 1c1c5a0 Thanks @​ardatan! - Prefer runtime description values over stale astNode descriptions in printSchemaWithDirectives / getDescriptionNode. Fixes #5508.

• #8423 0b9529f Thanks @​enisdenjo! - Fix prototype pollution in mergeDeep

  Source keys named __proto__, constructor or prototype are now skipped at every recursion level, and the check for an existing key uses hasOwnProperty instead of in, so inherited properties are never used as merge targets.

  Previously, merging untrusted data such as JSON.parse('{"constructor":{"__proto__":{"call":"x"}}}') could reach and overwrite properties on Object.prototype or Function.prototype.

12.0.0

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

... (truncated)

Commits

• 944121e Upcoming Release Changes (#8483)
• 19f5b33 fix(utils): compare path keys to proto at the property access (#8482)
• 3a43b4b Upcoming Release Changes (#8460)
• 20d36a5 fix(utils): block prototype pollution in mergeIncrementalResult paths
• b1fbba2 fix(deps): update dependency @​whatwg-node/promise-helpers to v2 (#8456)
• 77bbaec build(deps): bump the actions-deps group with 7 updates (#8434)
• 861011f build(deps): bump the actions-deps group with 6 updates (#8432)
• 8b9b7df chore(release): update monorepo packages versions (#8365)
• 0b9529f Fix prototype pollution in mergeDeep (#8423)
• 23ca392 chore(deps): update dependency graphql-scalars to v2 (#8385)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​graphql-tools/utils since your current version.

Updates @graphql-tools/merge from 8.4.2 to 9.2.6

Changelog

Sourced from @​graphql-tools/merge's changelog.

9.2.6

Patch Changes

• Updated dependencies [19f5b33]:
  • @​graphql-tools/utils@​12.0.3

9.2.5

Patch Changes

• #8467 20d36a5 Thanks @​ardatan! - Fix prototype pollution in mergeIncrementalResult

  Path segments are now rejected unless they are primitive strings or numbers, and keys named __proto__, constructor or prototype are still blocked. Previously a non-primitive segment such as ["__proto__"] bypassed the string equality guard and was coerced into a write on Object.prototype.

  Also exports shared isSafeObjectKey / isDangerousObjectKey helpers used by this path walker and other package call sites. @graphql-tools/merge and @graphql-tools/mock are patched so they ship with the new imports; updateInternalDependencies raises their utils floor when 12.0.2 is versioned.

• Updated dependencies [b1fbba2, 20d36a5]:

  • @​graphql-tools/utils@​12.0.2

9.2.4

Patch Changes

• #8367 2262087 Thanks @​ardatan! - Preserve multiple applications of the same directive when extending a type even if the repeatable directive definition is not present in the merge inputs.

• #8394 5523c4b Thanks @​bengry! - Write the synthesized default operation types back onto the schema definition node, so merging a schema extension that has no operation block (federation SDL, for example) still produces a query root on graphql@17.

• Updated dependencies [60db079, 57e316d, 1c1c5a0, 1c1c5a0, 0b9529f]:

  • @​graphql-tools/utils@​12.0.1

9.2.3

Patch Changes

• #8349 7fe0319 Thanks @​aarne! - Pass the collected directive definitions to mergeSchemaDefs so repeatable directives on schema definitions and extend schema extensions (e.g. a repeatable @link) are kept as separate instances instead of being collapsed and having their arguments merged.

• Updated dependencies [2273c21]:

  • @​graphql-tools/utils@​12.0.0

9.2.2

Patch Changes

• Updated dependencies [e90719b]:

... (truncated)

Commits

• 944121e Upcoming Release Changes (#8483)
• 3a43b4b Upcoming Release Changes (#8460)
• 20d36a5 fix(utils): block prototype pollution in mergeIncrementalResult paths
• 77bbaec build(deps): bump the actions-deps group with 7 updates (#8434)
• 861011f build(deps): bump the actions-deps group with 6 updates (#8432)
• 8b9b7df chore(release): update monorepo packages versions (#8365)
• 5523c4b fix(merge): don't drop the synthesized operation types on graphql 17 (#8394)
• 2262087 fix(merge): preserve multi-instance directives when extending types (#8367)
• 0f00a44 chore: use HTTPS git URLs for package repository metadata (#8376)
• 9feabd9 chore(release): update monorepo packages versions (#8327)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​graphql-tools/merge since your current version.

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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8938e681-22ce-4e28-b97b-826ad9e3c3cd

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}