fix(deps): update graphql-tools monorepo to v9 (major)

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-tools/delegate	^8.8.1 -> ^9.0.6
@graphql-tools/schema	^8.5.1 -> ^9.0.4

---

Release Notes

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

v9.0.6

Compare Source

Patch Changes

• Updated dependencies [43c736bd]:
  • @​graphql-tools/utils@​8.12.0
  • @​graphql-tools/batch-execute@​8.5.6
  • @​graphql-tools/schema@​9.0.4

v9.0.5

Compare Source

Patch Changes

• Updated dependencies [71cb4fae, 403ed450]:
  • @​graphql-tools/utils@​8.11.0
  • @​graphql-tools/batch-execute@​8.5.5
  • @​graphql-tools/schema@​9.0.3

v9.0.4

Compare Source

Patch Changes

• Updated dependencies [4fe3d9c0]:
  • @​graphql-tools/utils@​8.10.1
  • @​graphql-tools/batch-execute@​8.5.4
  • @​graphql-tools/schema@​9.0.2

v9.0.3

Compare Source

Patch Changes

• 0555a972 Thanks @​ardatan! - Bump versions

v9.0.2

Compare Source

Patch Changes

• #​4648 29ee7542 Thanks @​ardatan! - Do not call Transform.transformSchema more than once

v9.0.1

Compare Source

Patch Changes

• Updated dependencies [2609d71f]:
  • @​graphql-tools/utils@​8.10.0
  • @​graphql-tools/schema@​9.0.1
  • @​graphql-tools/batch-execute@​8.5.3

v9.0.0

Compare Source

Major Changes

• #​4566 d8dc67aa Thanks @​ardatan! - ## Breaking changes

  Schema generation optimization by removing transfomedSchema parameter

  Previously we were applying the transforms multiple times. We needed to introduced some breaking changes to improve the initial wrapped/stitched schema generation performance;

  • Transform.transformSchema no longer accepts transformedSchema which can easily be created with applySchemaTransforms(schema, subschemaConfig) instead.
  • Proxying resolver factory function that is passed as createProxyingResolver to SubschemaConfig no longer takes transformedSchema which can easily be created with applySchemaTransforms(schema, subschemaConfig) instead.

  stitchSchemas doesn't take nested arrays of subschemas

  stitchSchemas no longer accepts an array of arrays of subschema configuration objects. Instead, it accepts an array of subschema configuration objects or schema objects directly.

  stitchSchemas no longer prunes the schema with pruningOptions

  You can use pruneSchema from @graphql-tools/utils to prune the schema instead.

  stitchSchemas no longer respect "@​computed" directive if stitchingDirectivesTransformer isn't applied

  Also @graphql-tools/stitch no longer exports computedDirectiveTransformer and defaultSubschemaConfigTransforms. Instead, use @graphql-tools/stitching-directives package for @computed directive. Learn more about setting it up

  computedFields has been removed from the merged type configuration

  MergeTypeConfig.computedFields setting has been removed in favor of new computed field configuration written as:

  merge: {
    MyType: {
      fields: {
        myComputedField: {
          selectionSet: '{ weight }',
          computed: true,
        }
      }
    }
  }
  

  A field-level selectionSet specifies field dependencies while the computed setting structures the field in a way that assures it is always selected with this data provided. The selectionSet is intentionally generic to support possible future uses. This new pattern organizes all field-level configuration (including canonical) into a single structure.

Patch Changes

• #​4624 e3167edc Thanks @​n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

• Updated dependencies [8cc8721f, e3167edc]:

  • @​graphql-tools/schema@​9.0.0
  • @​graphql-tools/batch-execute@​8.5.2
  • @​graphql-tools/utils@​8.9.1

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

v9.0.4

Compare Source

Patch Changes

• Updated dependencies [43c736bd]:
  • @​graphql-tools/utils@​8.12.0
  • @​graphql-tools/merge@​8.3.6

v9.0.3

Compare Source

Patch Changes

• Updated dependencies [71cb4fae, 403ed450]:
  • @​graphql-tools/utils@​8.11.0
  • @​graphql-tools/merge@​8.3.5

v9.0.2

Compare Source

Patch Changes

• Updated dependencies [4fe3d9c0]:
  • @​graphql-tools/utils@​8.10.1
  • @​graphql-tools/merge@​8.3.4

v9.0.1

Compare Source

Patch Changes

• #​4643 2609d71f Thanks @​ardatan! - Revert the breaking change introduced in @graphql-tools/merge

• Updated dependencies [2609d71f]:

  • @​graphql-tools/utils@​8.10.0
  • @​graphql-tools/merge@​8.3.3

v9.0.0

Compare Source

Major Changes

• #​4463 8cc8721f Thanks @​ardatan! - Thanks @​mattkrick and @​borisno2!

---

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 becomes conflicted, or you tick the rebase/retry checkbox.

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

---

• [ ] If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.