chore(deps): bump graphql-tools from 6.0.14 to 8.0.0

[dependabot-preview[bot]]

Bumps graphql-tools from 6.0.14 to 8.0.0.

Release notes

Sourced from graphql-tools's releases.

graphql-tools@8.0.0

Major Changes

• 7d3e3006: BREAKING CHANGE
  • Now it only exports makeExecutableSchema from @graphql-tools/schema
  • Please migrate to scoped packages(@graphql-tools/*) because this npm package will no longer get updated

Patch Changes

• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
  • @​graphql-tools/schema@​8.0.0

@​graphql-tools/batch-execute@​8.0.0

Major Changes

• dae6dc7b: refactor: ExecutionParams type replaced by Request type

  rootValue property is now a part of the Request type.

  When delegating with delegateToSchema, rootValue can be set multiple ways:

  • when using a custom executor, the custom executor can utilize a rootValue in whichever custom way it specifies.
  • when using the default executor (execute/subscribe from graphql-js): -- rootValue can be passed to delegateToSchema via a named option -- rootValue can be included within a subschemaConfig -- otherwise, rootValue is inferred from the originating schema

  When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.

• c42e811d: BREAKING CHANGES;

  • Rename Request to ExecutionRequest
  • Add required operationType: OperationTypeNode field in ExecutionRequest
  • Add context in createRequest and createRequestInfo instead of delegateToSchema

  It doesn't rely on info.operation.operationType to allow the user to call an operation from different root type. And it doesn't call getOperationAST again and again to get operation type from the document/operation because we have it in Request and ExecutionParams ardatan/graphql-tools#3166

  Improvements;

  • Memoize defaultExecutor for a single GraphQLSchema so allow getBatchingExecutor to memoize batchingExecutor correctly.
  • And there is no different defaultExecutor is created for subscription and other operation types. Only one executor is used.

  Batch executor is memoized by executor reference but createDefaultExecutor didn't memoize the default executor so this memoization wasn't working correctly on batch-execute side. https://github.com/ardatan/graphql-tools/blob/remove-info-executor/packages/batch-execute/src/getBatchingExecutor.ts#L9

... (truncated)

Changelog

Sourced from graphql-tools's changelog.

8.0.0

Major Changes

• 7d3e3006: BREAKING CHANGE
  • Now it only exports makeExecutableSchema from @graphql-tools/schema
  • Please migrate to scoped packages(@graphql-tools/*) because this npm package will no longer get updated

Patch Changes

• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
• Updated dependencies [7d3e3006]
  • @​graphql-tools/schema@​8.0.0

7.0.5

Patch Changes

• 52971f4e: fix(graphql-tools): provide @​apollo/client as an optional package
• Updated dependencies [eae28793]
  • @​graphql-tools/merge@​6.2.14

7.0.4

Patch Changes

• Revert mock package to v7 to avoid breaking changes

7.0.3

Patch Changes

• Updated dependencies [24926654]
• Updated dependencies [24926654]
• Updated dependencies [24926654]
  • @​graphql-tools/delegate@​7.0.10
  • @​graphql-tools/stitch@​7.3.0
  • @​graphql-tools/links@​7.0.4
  • @​graphql-tools/mock@​8.0.0

7.0.2

Patch Changes

• fb14cd28: Added export from new optimize package
• Updated dependencies [fb14cd28]
  • @​graphql-tools/optimize@​1.0.1

... (truncated)

Commits

• 7681cdc chore(release): update monorepo packages versions (#3011)
• 7d3e300 Huge cleanup before major release (breaking) (#3081)
• 5b4df36 fix(deps): update dependency tslib to ~2.3.0 (#3067)
• ce919f3 ESM Support
• 67a72cb chore(release): update monorepo packages versions (#2943)
• 52971f4 fix(graphql-tools): provide @​apollo/client as an optional package
• 0338f98 fix(deps): update dependency tslib to ~2.2.0 (#2800)
• a82aa0d fix(graphql-tools-npm): Revert mock package to v7 to avoid breaking changes
• 42d72ad [deploy_website] Spelling (#2598)
• 179dd27 chore(release): update monorepo packages versions (#2545)
• Additional commits viewable in compare view

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.

If all status checks pass Dependabot will automatically merge this pull request.

---

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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• ci/circleci: test

Dependabot will still automatically merge this pull request if you amend it and your tests pass.